Summary: | Unhandled Instruction Bytes (vmovdqu, "0xC5 0xFA 0x6F 0x2") | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Jeffrey Walton <noloader> |
Component: | memcheck | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | minor | ||
Priority: | NOR | ||
Version: | 3.10.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jeffrey Walton
2015-11-12 10:10:00 UTC
That's an AVX instruction, which isn't supported by the x86 (32-bit) front end. x86 (32-bit) only supports up to SSSE3. I suggest you move to 64-bit x86 instead, which supports up to and including AVX2. (In reply to Julian Seward from comment #1) > That's an AVX instruction, which isn't supported by the x86 (32-bit) front > end. > x86 (32-bit) only supports up to SSSE3. I suggest you move to 64-bit x86 > instead, > which supports up to and including AVX2. Something sounds amiss. We test under both i686 and x86_64. If vmovdqu is x86_64, then it seems like the test program should SIGILL rather than complete successfully. I think we might be talking at cross purposes. Sure, the silicon supports VMOVDQU (and other AVX insns) in both 32- and 64-bit modes. What I meant is, Valgrind doesn't; 32-bit support doesn't extend beyond SSSE3. If you want to run AVX code on Valgrind then you need to do it in a 64-bit process. (In reply to Julian Seward from comment #3) > I think we might be talking at cross purposes. Sure, the silicon supports > VMOVDQU > (and other AVX insns) in both 32- and 64-bit modes. What I meant is, > Valgrind > doesn't; 32-bit support doesn't extend beyond SSSE3. If you want to run AVX > code > on Valgrind then you need to do it in a 64-bit process. Oh, my bad. Yes, I was disconnected. Sorry about that. |