On 1/6/2023 1:27 PM, Jason Lowe-Power via gem5-users wrote:
Hi Eliot,
Unfortunately, I don't have a direct answer for you. However, I want to say that I appreciate you
keeping the mailing list updated with your progress!
Thank you for the encouragement, Jason!
At this point I probably need t
Hi Eliot,
Unfortunately, I don't have a direct answer for you. However, I want to say
that I appreciate you keeping the mailing list updated with your progress!
Cheers,
Jason
On Fri, Jan 6, 2023 at 10:07 AM Eliot Moss via gem5-users <
gem5-users@gem5.org> wrote:
> On 1/4/2023 11:51 PM, Eliot Mo
On 1/4/2023 11:51 PM, Eliot Moss via gem5-users wrote:
So, what I have found is that the bad micro-op is coming from trying to execute the micro-ops of an
INT3 macro-instruction. The end of the sequence consists of the micro-ops:
andi t0, t5, 0x1
br 0x803d
br 0x80b8
followed by a bunch of "pa
So, what I have found is that the bad micro-op is coming from trying to execute the micro-ops of an
INT3 macro-instruction. The end of the sequence consists of the micro-ops:
andi t0, t5, 0x1
br 0x803d
br 0x80b8
followed by a bunch of "panic" micro-ops. t5 holds an m5 register,
where the low
On 1/3/2023 11:15 PM, Hoa Nguyen via gem5-users wrote:
I believe you can compile build/X86/gem5.debug to have all the symbols
available for debugging.
Yes, they are. I dont think that's the issue.
I'm not sure about the error, but generally, when debugging an instruction, I would try to fin
Hi,
I believe you can compile build/X86/gem5.debug to have all the symbols
available for debugging.
I'm not sure about the error, but generally, when debugging an instruction,
I would try to find the internal name of the instruction in gem5, and look
at gem5/build/X86/arch/x86/arch/generated/ to
