Hi Nikos,
Thanks once again. I figured that out.
Can you help me in getting instruction trace for ALU ? I tried doing this for
X86 system.
What I am trying to do us to get instruction traces for ALU.
What I did:
There is a file, regop.isa (src/arch/x86/isa/microops/). In this file, at line
Hi Riddhi,
Indeed, this is what the DDUMP() macro does, you can either use that or do it
on your own.
Nikos
From: gem5-users on behalf of Google
Reply-To: gem5 users mailing list
Date: Tuesday, 10 July 2018 at 09:05
To: "gem5-users@gem5.org"
Subject: Re: [gem5-users] size variable in
Hi Nikos,
Thanks for your prompt reply. I have one more doubt. Suppose the size of the
packet is 64 bytes, and the pointer from getConstPtr() will point to 1
byte data, so for getting all the 64 bytes data, I have to increment this
pointer, right?
Thanks in advance.
Regards,
Riddhi
Sent
Hi Riddhi,
The size field in the packet class is in bytes. To print the data of a packet
you could use the following:
DDUMP(Flag, pkt->getConstPtr(), pkt->getSize());
Where Flag is the debugging flag that will enable the print and pkt is the
packet you want to print. You will also need to
Hi all,
I am asking a very basic question but I am confused as to what the size
variable in Packet class represents. When I ran dram/sweep.py config file, I
saw that the size turns out to 1,4,8, and 64 for different cases. In the
packet.hh, the comment says that size represents the size of
