[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #6 from Jérôme Carretero --- Workaround for the particular Qt 5.11 scenario: compiling qtcore with CXXFLAGS+=" -mno-rdrnd". -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #5 from Tom Hughes --- Well running a program that's hard coded to use it on a CPU that doesn't support it is always going to fail, so don't do that... Valgrind runs your program on an emulated CPU that is normally close to, but not identical to, your actual CPU which is why we adjust the CPUID to indicate what features are actually available. Unless you're only planning to run your program on specific hardware then it really needs to check this kind of thing at run time anyway. *** This bug has been marked as a duplicate of bug 353370 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #4 from Jérôme Carretero --- Tested with the now's SVN, it's still unhandled. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #3 from Jérôme Carretero --- actually, that issues disables advertising rdrand in CPUID, but what if the program is hard-coded to use it... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #2 from Jérôme Carretero --- Might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=353370 but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396176] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6
https://bugs.kde.org/show_bug.cgi?id=396176 --- Comment #1 from Jérôme Carretero --- It's rdrand32_step (used as a gcc built-in) vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x6 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==30590== valgrind: Unrecognised instruction at address 0x846054f. ==30590==at 0x846054F: _rdrand32_step (immintrin.h:109) ==30590==by 0x846054F: qt_random_cpu (qrandom.cpp:114) ==30590==by 0x846054F: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (qrandom.cpp:369) -- You are receiving this mail because: You are watching all bug changes.
