> vex amd64->IR: unhandled instruction bytes: 0xC4 0xC2 0x7D 0x2E 0x8 0x49 0x83
> 0xC0
-----foo.S
.byte 0xC4,0xC2,0x7D,0x2E,0x8,0x49,0x83,0xC0
-----
$ gcc -c foo.S
$ gdb foo.o
(gdb) x/i 0
0x0: vmaskmovps %ymm1,%ymm0,(%r8)
> ==29091== 2. The instruction is legitimate but Valgrind doesn't handle it,
> ==29091== i.e. it's Valgrind's fault. If you think this is the case or
> ==29091== you are not sure, please let us know and we'll try to fix it.
File a bug [request for enhancement] at
https://bugs.kde.org/enter_bug.cgi?product=valgrind .
Please mention the version of all software involved, which Linux distribution,
etc.
In the meantime, use software which is not so highly optimized.
If that is your software, then remove "-O2", don't write assembly language, etc.
If that is an add-on shared library, then ask the supplier,
or change to an equivalent but not-so-optimized library.
If that is a built-in library such as [g]libc
then use a different Linux distribution which is not so aggressively optimized.
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
