error 0
 ==26474== Memcheck, a memory error detector
 ==26474== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
 ==26474== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright info
 ==26474== Command: ./try
 ==26474==
 vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF7 0xF 0x92 0xC0 0x83 0xEA 0x1
 vex amd64->IR:   REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0
 vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
 vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
 ==26474== valgrind: Unrecognised instruction at address 0x111988.
 ==26474==    at 0x111988: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x10B2E3: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x10AA92: crypto_sign_ed448goldilocks_32_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x109683: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x109094: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474== Your program just tried to execute an instruction that Valgrind
 ==26474== did not recognise.  There are two possible reasons for this.
 ==26474== 1. Your program has a bug and erroneously jumped to a non-code
 ==26474==    location.  If you are running Memcheck and you just saw a
 ==26474==    warning about a bad jump, it's probably your program's fault.
 ==26474== 2. The instruction is legitimate but Valgrind doesn't handle it,
 ==26474==    i.e. it's Valgrind's fault.  If you think this is the case or
 ==26474==    you are not sure, please let us know and we'll try to fix it.
 ==26474== Either way, Valgrind will now raise a SIGILL signal which will
 ==26474== probably kill your program.
 ==26474==
 ==26474== Process terminating with default action of signal 4 (SIGILL)
 ==26474==  Illegal opcode at address 0x111988
 ==26474==    at 0x111988: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x10B2E3: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x10AA92: crypto_sign_ed448goldilocks_32_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x109683: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==    by 0x109094: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==26474==
 ==26474== HEAP SUMMARY:
 ==26474==     in use at exit: 44,640 bytes in 10 blocks
 ==26474==   total heap usage: 20 allocs, 10 frees, 67,544 bytes allocated
 ==26474==
 ==26474== LEAK SUMMARY:
 ==26474==    definitely lost: 0 bytes in 0 blocks
 ==26474==    indirectly lost: 0 bytes in 0 blocks
 ==26474==      possibly lost: 44,640 bytes in 10 blocks
 ==26474==    still reachable: 0 bytes in 0 blocks
 ==26474==         suppressed: 0 bytes in 0 blocks
 ==26474== Rerun with --leak-check=full to see details of leaked memory
 ==26474==
 ==26474== For lists of detected and suppressed errors, rerun with: -s
 ==26474== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)