Summary: | cvtps2pd with redundant RexW: vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0x5A 0x7 0x48 0xF 0x5A 0x4F | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Nathan Stratton <nathan> |
Component: | vex | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | griffin.k.myers+kde, kroser, mark, mendola, nathan, patrick.noffke, tom |
Priority: | NOR | ||
Version: | 3.7 SVN | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Fix relative to 3.8.1 release
Fix relative to current SVN HEAD (r2755) redundantRexW testcase extension for cvtps2pd |
Description
Nathan Stratton
2011-07-29 01:08:49 UTC
This is a CVTPS2PD instruction. The problem is the 0x48 (REX.W) prefix which we're not expecting - it is likely redundant. *** Bug 288274 has been marked as a duplicate of this bug. *** Same here with valgrind 3.8.1: vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0x5A 0x7 0x48 0xF 0x5A 0x4F vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 Created attachment 82243 [details]
Fix relative to 3.8.1 release
The attached minor change to guest_amd64_toIR.c resolves this issue for me when running with IPP under valgrind 3.8.1.
Created attachment 82244 [details]
Fix relative to current SVN HEAD (r2755)
And furthermore, here is a second patch which fixes this relative to the current SVN HEAD (r2755). There is no difference between the two patches other than the relevant line numbers.
I have the exact same output as Gaetano reported in comment #4. The patch from Griffin Myers works for me. Created attachment 94921 [details]
redundantRexW testcase extension for cvtps2pd
I think ignoring the REX.W for cvtps2pd is correct. I cannot find anything that explains what it really means. Attached is an extension to the none/tests/amd64/redundantRexW testcase that seems to confirm it.
*** Bug 329245 has been marked as a duplicate of this bug. *** VEX svn r3198 valgrind svn r15699 |