[valgrind] [Bug 369264] New: Fedora 24 i686 and vex x86->IR: unhandled instruction bytes: 0xC5 0xF8 0x10 0x3

https://bugs.kde.org/show_bug.cgi?id=369264 Bug ID: 369264 Summary: Fedora 24 i686 and vex x86->IR: unhandled instruction bytes: 0xC5 0xF8 0x10 0x3 Product: valgrind Version: 3.12 SVN Platform: Other OS: Lin

[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 meant is, > Valgrind

[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 64-bit x86 > instead,

[valgrind] [Bug 366464] disInstr(arm): unhandled instruction: 0xF1010200

https://bugs.kde.org/show_bug.cgi?id=366464 --- Comment #3 from Jeffrey Walton --- (In reply to Peter Maydell from comment #2) > 0xF1010200 is "SETEND BE". This is almost certainly the optimized-for-1176 > 32-bit ARM raspberry pi memcmp. See bug #322935, closed WONTFIX in 2013. Ah, thanks Peter.

[valgrind] [Bug 366464] New: disInstr(arm): unhandled instruction: 0xF1010200

https://bugs.kde.org/show_bug.cgi?id=366464 Bug ID: 366464 Summary: disInstr(arm): unhandled instruction: 0xF1010200 Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severi

[valgrind] [Bug 366344] Multiple unhandled instruction for Aarch64 (0x0EE0E020, 0x1AC15800, 0x4E284801, 0x5E040023, 0x5E056060)

https://bugs.kde.org/show_bug.cgi?id=366344 --- Comment #6 from Jeffrey Walton --- (In reply to Julian Seward from comment #4) > (In reply to Jeffrey Walton from comment #1) > > It looks like 3.12-SVN is missing the some of the instructions for the CRC32 > > checks: > > > ARM64 front end: data_p

[valgrind] [Bug 366344] Multiple unhandled instruction for Aarch64 (0x0EE0E020, 0x1AC15800, 0x4E284801, 0x5E040023, 0x5E056060)

https://bugs.kde.org/show_bug.cgi?id=366344 --- Comment #1 from Jeffrey Walton --- It looks like 3.12-SVN is missing the some of the instructions for the CRC32 checks: $ valgrind ./cryptest.exe v ==9653== Memcheck, a memory error detector ==9653== Copyright (C) 2002-2015, and GNU GPL'd, by Julia

[valgrind] [Bug 366345] New: Dirty compile from m_libcbase.c and vgdb-invoker-ptrace.c

https://bugs.kde.org/show_bug.cgi?id=366345 Bug ID: 366345 Summary: Dirty compile from m_libcbase.c and vgdb-invoker-ptrace.c Product: valgrind Version: 3.12 SVN Platform: Other OS: other Status:

[valgrind] [Bug 366344] New: Multiple unhandled instruction for Aarch64 (0x0EE0E020, 0x1AC15800, 0x4E284801, 0x5E040023, 0x5E056060)

https://bugs.kde.org/show_bug.cgi?id=366344 Bug ID: 366344 Summary: Multiple unhandled instruction for Aarch64 (0x0EE0E020, 0x1AC15800, 0x4E284801, 0x5E040023, 0x5E056060) Product: valgrind Version: 3.11.0

[valgrind] [Bug 358620] ARM: unhandled syscall: 357

https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #6 from Jeffrey Walton --- This may matter: $ echo $CFLAGS -DNDEBUG -g2 -O3 -march=armv8-a+crc -mtune=cortex-a53 -mfpu=crypto-neon-fp-armv8 -mfloat-abi=hard $ echo $CXXFLAGS -DNDEBUG -g2 -O3 -march=armv8-a+crc -mtune=cortex-a53 -mfpu=crypt

[valgrind] [Bug 358620] ARM: unhandled syscall: 357

https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #5 from Jeffrey Walton --- > This is with 3.7.0, which is really old now. Can you try again with 3.11.0 or > better with the current SVN trunk? It is still present in the trunk. raspberrypi:botan$ valgrind ./botan-test ==22114== Memcheck

[valgrind] [Bug 358620] ARM: unhandled syscall: 357

https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #4 from Jeffrey Walton --- > This is with 3.7.0, which is really old now. Can you try again with 3.11.0 or > better with the current SVN trunk? The issue is present when building 3.11 from sources: raspberrypi:botan$ valgrind ./botan-test

[valgrind] [Bug 358620] ARM: unhandled syscall: 357

https://bugs.kde.org/show_bug.cgi?id=358620 Jeffrey Walton changed: What|Removed |Added CC||noloa...@gmail.com -- You are receiving this

[valgrind] [Bug 358856] unhandled instruction bytes: 0xC4 0xE2 0x7B 0xF7

https://bugs.kde.org/show_bug.cgi?id=358856 Jeffrey Walton changed: What|Removed |Added Version|unspecified |3.11.0 -- You are receiving this mail because

[valgrind] [Bug 358856] unhandled instruction bytes: 0xC4 0xE2 0x7B 0xF7

https://bugs.kde.org/show_bug.cgi?id=358856 --- Comment #1 from Jeffrey Walton --- The processor is a Core-i5-5200U. The Core-i5-5200U was purchased to test the RDRAND and RDSEED instructions. It looks like SHRX is part of BMI2 (http://en.wikipedia.org/wiki/Bit_Manipulation_Instruction_Sets). BM

[valgrind] [Bug 358856] New: unhandled instruction bytes: 0xC4 0xE2 0x7B 0xF7

https://bugs.kde.org/show_bug.cgi?id=358856 Bug ID: 358856 Summary: unhandled instruction bytes: 0xC4 0xE2 0x7B 0xF7 Product: valgrind Version: unspecified Platform: Compiled Sources URL: http://pastebin.com/mx3hJKtV

[valgrind] [Bug 273475] Add support for AVX instructions

https://bugs.kde.org/show_bug.cgi?id=273475 Jeffrey Walton changed: What|Removed |Added CC||noloa...@gmail.com -- You are receiving this

[valgrind] [Bug 357734] New: "unhandled instruction 0x1AC12D8C" for ARM64/AARCH64

https://bugs.kde.org/show_bug.cgi?id=357734 Bug ID: 357734 Summary: "unhandled instruction 0x1AC12D8C" for ARM64/AARCH64 Product: valgrind Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED