Hi Mohammad,

I think it also produces the value of the operands. For instance, look
at this trace (slightly cropped to avoid useless information for the case):

inc    DS:[rbp + 0xfffffffffffffff8]
INC_M : ldst   t1, DS:[rbp + 0xfffffffffffffff8] : MemRead :  
D=0x0000000000079a8f A=0x7fffffffeb78  
INC_M : addi   t1, t1, 0x1 : IntAlu :  D=0x0000000000000000
INC_M : st   t1, DS:[rbp + 0xfffffffffffffff8] : MemWrite :  
D=0x0000000000079a90 A=0x7fffffffeb78

D is one of the operands, you can see how its value is incremented at
the end of the operation.

Ferran O.

On 04/05/17 17:36, Mohammad Khasawneh wrote:
>
> Thank you, Ferran. I just tried a run with the ExecAll flag, it
> produces a good amount of information but not exactly what I need. I
> need to get the exact values of the operands not only the register
> names or addresses.
>
>  
>
> Thanks,
>
> Mohammad
>
>  
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>  
>
> *From: *Ferran Olid <mailto:[email protected]>
> *Sent: *Thursday, May 4, 2017 11:26 AM
> *To: *[email protected] <mailto:[email protected]>
> *Subject: *Re: [gem5-users] Dumping instruction operands
>
>  
>
> Hi Mohammad,
>
> Have you tried using the debug options with "ExecAll"? If I didn't
> understand you wrong, this is what you're looking for.
>
> Cheers,
>
> Ferran O.
>
> On 04/05/17 17:21, Mohammad Khasawneh wrote:
>
>     Hello all,
>
>      
>
>     I’m trying to figure out a way to dump an instruction’s type,
>     operand, and results. I found that in the iew stage right before
>     the instruction is sent for execution I have access to its
>     physical register numbers, and the register accessor functions in
>     dyn_inst may allow me to read its operands. I still need to print
>     its final result though after it returns from execution, which I
>     can probably do with two dumps, one before the call to execute and
>     one after.
>
>      
>
>     Is there a more direct method I am missing on?
>
>      
>
>     Thanks,
>     Mohammad
>
>
>
>
>     _______________________________________________
>
>     gem5-users mailing list
>
>     [email protected] <mailto:[email protected]>
>
>     http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
>  
>
>  
>
>
>
> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to