https://bugs.kde.org/show_bug.cgi?id=438871
Simon Sobisch <simonsobi...@gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #6 from Simon Sobisch <simonsobi...@gnu.org> ---
(In reply to Tom Hughes from comment #5)
> Created attachment 139502 [details]
> Patch to ignore REX.W for MOVDQU
>
> Try this patch and see if it helps...
Yes, brought me directly to the next one:
vx amd64->IR: unhandled instruction bytes: 0xF3 0x49 0xF 0x7F 0x4B 0xE0 0xF3
0x49 0xF 0x7F
vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=1
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=1
Following the lead with the patch I've did the same for the 0x7F case /* F3 0F
7F = MOVDQU -- move from G (xmm) to E (mem or xmm). */
allowing a size of either 4 or 8 - now the application can be run with
valgrind.
Thank you very much - I hope those two patches are well enough to get into the
next release.
--
You are receiving this mail because:
You are watching all bug changes.
