Bug 404069 - vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22
Summary: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (other bugs)
Version First Reported In: 3.14.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-07 20:49 UTC by stayprivate
Modified: 2019-03-10 09:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description stayprivate 2019-02-07 20:49:49 UTC 
SUMMARY

vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22

STEPS TO REPRODUCE
1. With gcc8 compile some code with -m32 -msse4.2 -mfpmath=sse -march=nehalem -mtune=sandybridge
2. Run code on Ubuntu18/AmdThreadRipper (I'm using valgrind_threadcheck
3. 

OBSERVED RESULT

Messaged 
 vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22

EXPECTED RESULT

No invalide instruction ;-)


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma:  Ubuntu 18.04
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

I found this reference to a similar problem at Bug 276780, with a patchl

I applied the patch, and got further but now i'm getting:

 vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xA

Got the source from git and the above mentionned patch is nowhere to be found in the master branch, so not looking like this bug is fixed.

Regards
Comment 1 Julian Seward 2019-03-10 09:54:27 UTC 
Try removing -msse4.2 -mfpmath=sse -march=nehalem -mtune=sandybridge and
instead use run-time CPUID-based feature detection.