Bug 375008 - amd64->IR: unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xD8 0x4 0x4 0x0 0x0 0x8F
Summary: amd64->IR: unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xD8 0x4 0x4 0x0 ...
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: 3.13 SVN
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-13 14:44 UTC by dcb314
Modified: 2017-05-05 17:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed 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 dcb314 2017-01-13 14:44:27 UTC 
Switch on -march=native in a gcc build on a AMD 8350, and I got this:

vex amd64->IR: unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xD8 0x4 0x4 0x0 0x0 0x8F
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.nVVVV=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0

$ ./valgrind/results/bin/valgrind --version
valgrind-3.13.0.SVN
$
Comment 1 Ivo Raisr 2017-05-05 16:11:52 UTC 
Thank you for the report.
We need the unhandled instruction - can you obtain it for example by gdb or objdump?
Comment 2 dcb314 2017-05-05 17:07:19 UTC 
Not sure what you are asking for.

I think the unhandled instruction is  0x8F 0x6A 0x78 0x10 0xD8 0x4 0x4 0x0 0x0 0x8F and so an arch reference manual (or wikipedia) will tell you which
instruction those bytes are.