On 22/08/13 20:58, janjust wrote: > If certain instructions are not detected through configure process, does > that imply that a valgrind build will not be configured to handle these > instructions (i.e. fail at runtime)?
No - those tests mostly only govern which bits of the test suite will be built and run. The actual emulation engine checks at run time which instructions are supported. > 21 vex amd64->IR: unhandled instruction bytes: 0xC4 0xE3 0xF1 0x6B 0x15 0x12 > 0x4 0x0 > 22 vex amd64->IR: REX=0 REX.W=1 REX.R=0 REX.X=0 REX.B=0 > 23 vex amd64->IR: VEX=1 VEX.L=0 VEX.nVVVV=0x1 ESC=0F3A > 24 vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 > 25 3=0 That (in effect 66 0F 3A 6B) appears to be undefined in the latest Intel manual so I'm guessing it's some AMD extension... That said it doesn't seem to be defined in the AMD manual either which is a little confusing... Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
