[valgrind] [Bug 355231] Unhandled Instruction Bytes (vmovdqu, "0xC5 0xFA 0x6F 0x2")

https://bugs.kde.org/show_bug.cgi?id=355231 --- Comment #4 from Jeffrey Walton --- (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

[valgrind] [Bug 355231] Unhandled Instruction Bytes (vmovdqu, "0xC5 0xFA 0x6F 0x2")

https://bugs.kde.org/show_bug.cgi?id=355231 --- Comment #3 from Julian Seward --- 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

[valgrind] [Bug 355231] Unhandled Instruction Bytes (vmovdqu, "0xC5 0xFA 0x6F 0x2")

https://bugs.kde.org/show_bug.cgi?id=355231 --- Comment #2 from Jeffrey Walton --- (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

[valgrind] [Bug 355231] Unhandled Instruction Bytes (vmovdqu, "0xC5 0xFA 0x6F 0x2")

https://bugs.kde.org/show_bug.cgi?id=355231 Julian Seward changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED