|
From: Jordan M. C. <jc...@li...> - 2010-06-21 21:53:01
|
I have actually tried both the trace-flags option as well as the profile-flags option and the results that Valgrind returns are not what I expected. Trace just shows basic block printout information and profile-flags seems to show assembly to the actual translation of the code back to hardware assembly. I am really looking for the actual translation of test code I wrote in the translated VEX format before it gets translated to the hardware assembly. I am not sure if that is even a debug feature so it might be a moot point.
Thanks for your time,
Jordan
________________________________
From: Greg Parker [gp...@ap...]
Sent: Monday, June 21, 2010 3:32 PM
To: Jordan M. Cramer
Cc: val...@li...
Subject: Re: [Valgrind-developers] Implementing PowerPC instruction in VEX
On Jun 21, 2010, at 1:06 PM, Jordan M. Cramer wrote:
I have begun working on trying to implement some instructions currently not handled by Valgrind for the powerpc architecture involving such instructions as lfpdx where two parallel fpu are used to take in a quadword load data. So far I understand mostly how VEX translates the original code given but I would like to know if there is a way to dump the assembly information that VEX creates before it translates back to the assembly code for that specific hardware implementation. Is there some sort of debugger option that allows you to see what the dump information is right before it translates back to assembly for the given hardware?
Yes. Use the --trace-flags option to log any of VEX's intermediate states or output.
>From the command-line help:
"--trace-flags and --profile-flags values (omit the middle space):
1000 0000 show conversion into IR
0100 0000 show after initial opt
0010 0000 show after instrumentation
0001 0000 show after second opt
0000 1000 show after tree building
0000 0100 show selecting insns
0000 0010 show after reg-alloc
0000 0001 show final assembly
(Nb: you need --trace-notbelow with --trace-flags for full details)"
--
Greg Parker gp...@ap...<mailto:gp...@ap...> Runtime Wrangler
|