libkeccak makepkg errors

gistfile1.txt

==> Starting check()...
==31928== Memcheck, a memory error detector
==31928== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==31928== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==31928== Command: bin/test
==31928== 
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xC9 0x3 0x1D 0x0 0x0 0xF3
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==31928== valgrind: Unrecognised instruction at address 0x4e3ed30.
==31928==    at 0x4E3ED30: libkeccak_state_initialise (in /tmp/makepkg/libkeccak/src/libkeccak-1.1.1/bin/libkeccak.so.1.1)
==31928==    by 0x40117C: main (in /tmp/makepkg/libkeccak/src/libkeccak-1.1.1/bin/test)
==31928== Your program just tried to execute an instruction that Valgrind
==31928== did not recognise.  There are two possible reasons for this.
==31928== 1. Your program has a bug and erroneously jumped to a non-code
==31928==    location.  If you are running Memcheck and you just saw a
==31928==    warning about a bad jump, it's probably your program's fault.
==31928== 2. The instruction is legitimate but Valgrind doesn't handle it,
==31928==    i.e. it's Valgrind's fault.  If you think this is the case or
==31928==    you are not sure, please let us know and we'll try to fix it.
==31928== Either way, Valgrind will now raise a SIGILL signal which will
==31928== probably kill your program.
==31928== 
==31928== Process terminating with default action of signal 4 (SIGILL): dumping core
==31928==  Illegal opcode at address 0x4E3ED30
==31928==    at 0x4E3ED30: libkeccak_state_initialise (in /tmp/makepkg/libkeccak/src/libkeccak-1.1.1/bin/libkeccak.so.1.1)
==31928==    by 0x40117C: main (in /tmp/makepkg/libkeccak/src/libkeccak-1.1.1/bin/test)
==31928== 
==31928== HEAP SUMMARY:
==31928==     in use at exit: 288 bytes in 1 blocks
==31928==   total heap usage: 2 allocs, 1 frees, 4,384 bytes allocated
==31928== 
==31928== LEAK SUMMARY:
==31928==    definitely lost: 0 bytes in 0 blocks
==31928==    indirectly lost: 0 bytes in 0 blocks
==31928==      possibly lost: 0 bytes in 0 blocks
==31928==    still reachable: 288 bytes in 1 blocks
==31928==         suppressed: 0 bytes in 0 blocks
==31928== Reachable blocks (those to which a pointer was found) are not shown.
==31928== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==31928== 
==31928== For counts of detected and suppressed errors, rerun with: -v
==31928== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
make: *** [Makefile:232: check] Illegal instruction (core dumped)
==> ERROR: A failure occurred in check().
    Aborting...

That's weird, there is no assembly code so I don't now where the illegal opcode could be.
Try running the test without valgrind.

getting the same thing :(