error 0
 ==30104== Memcheck, a memory error detector
 ==30104== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
 ==30104== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright info
 ==30104== Command: ./try
 ==30104==
 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
 ==30104== valgrind: Unrecognised instruction at address 0x111d28.
 ==30104==    at 0x111D28: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x10B003: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x10A8B2: crypto_dh_ed448goldilocks_64_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x1096F8: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x1090D4: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104== Your program just tried to execute an instruction that Valgrind
 ==30104== did not recognise.  There are two possible reasons for this.
 ==30104== 1. Your program has a bug and erroneously jumped to a non-code
 ==30104==    location.  If you are running Memcheck and you just saw a
 ==30104==    warning about a bad jump, it's probably your program's fault.
 ==30104== 2. The instruction is legitimate but Valgrind doesn't handle it,
 ==30104==    i.e. it's Valgrind's fault.  If you think this is the case or
 ==30104==    you are not sure, please let us know and we'll try to fix it.
 ==30104== Either way, Valgrind will now raise a SIGILL signal which will
 ==30104== probably kill your program.
 ==30104==
 ==30104== Process terminating with default action of signal 4 (SIGILL)
 ==30104==  Illegal opcode at address 0x111D28
 ==30104==    at 0x111D28: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x10B003: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x10A8B2: crypto_dh_ed448goldilocks_64_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x1096F8: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==    by 0x1090D4: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==30104==
 ==30104== HEAP SUMMARY:
 ==30104==     in use at exit: 4,800 bytes in 12 blocks
 ==30104==   total heap usage: 22 allocs, 10 frees, 30,008 bytes allocated
 ==30104==
 ==30104== LEAK SUMMARY:
 ==30104==    definitely lost: 0 bytes in 0 blocks
 ==30104==    indirectly lost: 0 bytes in 0 blocks
 ==30104==      possibly lost: 4,800 bytes in 12 blocks
 ==30104==    still reachable: 0 bytes in 0 blocks
 ==30104==         suppressed: 0 bytes in 0 blocks
 ==30104== Rerun with --leak-check=full to see details of leaked memory
 ==30104==
 ==30104== For lists of detected and suppressed errors, rerun with: -s
 ==30104== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)