Version:           3.6.0
OS:                Linux

Valgrind always terminates with an unhandled instruction error:
'vex amd64->IR: unhandled instruction bytes: 0xC5 0xF9 0x28 0xD0 0xC5 0xFB'

Reproducible: Didn't try

Steps to Reproduce:
'valgrind ./foo'

Actual Results:  
Console output as below:

vex amd64->IR: unhandled instruction bytes: 0xC5 0xF9 0x28 0xD0 0xC5 0xFB
==23054== valgrind: Unrecognised instruction at address 0x7213f54.
==23054== Your program just tried to execute an instruction that Valgrind
==23054== did not recognise.  There are two possible reasons for this.
==23054== 1. Your program has a bug and erroneously jumped to a non-code
==23054==    location.  If you are running Memcheck and you just saw a
==23054==    warning about a bad jump, it's probably your program's fault.
==23054== 2. The instruction is legitimate but Valgrind doesn't handle it,
==23054==    i.e. it's Valgrind's fault.  If you think this is the case or
==23054==    you are not sure, please let us know and we'll try to fix it.
==23054== Either way, Valgrind will now raise a SIGILL signal which will
==23054== probably kill your program.
==23054== 
==23054== Process terminating with default action of signal 4 (SIGILL): dumping core
==23054==  Illegal opcode at address 0x7213F54
==23054==    at 0x7213F54: log (in /lib64/libm-2.13.so)
==23054==    by 0x9023630: ??? (in /usr/lib64/libnvidia-glcore.so.285.05.09)
==23054==    by 0xB62322F: ???
==23054==    by 0xB4C6FFF: ??? (in /usr/lib64/gconv/ISO8859-1.so)
==23054==    by 0xA2764DF: ???
==23054==    by 0x90C33CF: ??? (in /usr/lib64/libnvidia-glcore.so.285.05.09)
==23054==    by 0xA2764DF: ???
==23054==    by 0x94DD656: ??? (in /usr/lib64/libnvidia-glcore.so.285.05.09)
==23054==    by 0xA2764DF: ???
==23054==    by 0xB50037F: ???
==23054==    by 0xB4C6FFF: ??? (in /usr/lib64/gconv/ISO8859-1.so)
==23054==    by 0x902F94D: ??? (in /usr/lib64/libnvidia-glcore.so.285.05.09)


Expected Results:  
 

Disassembly indicates an instruction similar to: vmovapd %xmm0,%xmm2