On Monday, June 04, 2012, Eliot Moss wrote:
> unhandled here). A quick look suggests that this is a PADDB instruction.
Yes, 64-bit (MMX) PADDB. Problem is it has a redundant REX prefix
(IPP is very strong on those, for some reason), and Valgrind pretty
much rejects all redundant REX prefixes.
Marc, in guest_amd64_toIR.c find this
case 0xFC:
case 0xFD:
case 0xFE: /* PADDgg (src)mmxreg-or-mem, (dst)mmxreg */
if (sz != 4)
goto mmx_decode_failure;
delta = dis_MMXop_regmem_to_reg ( vbi, pfx, delta, opc, "padd", True
);
break;
and change (sz != 4) to (sz != 4 && sz != 8). That might help.
J
> I think someone has been working on adding some of those instructions
> latelt; it *might* be covered if you grab and build from svn head.
>
> Regards -- Eliot Moss (a fellow user and occasional patch contributor)
>
> ---------------------------------------------------------------------------
> --- Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Valgrind-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
