Re: [gem5-users] Double PseudoInst commands while running Parsec

If no one has any better ideas, I'd try to use GDB on the gem5 executable itself, turn on ExecAll logging, and break on the stat dump part of the code and see where both calls come from. Also consider Mozilla rr reverse debugging if it seems that reverse stepping could help. Not ideal, but works e

Re: [gem5-users] Double PseudoInst commands while running Parsec

Thanks for your response. Double checked. There doesn't seem to be a problem with the executable. attached are the disassembly of the ROI begin and end functions and the original code. I have debugged with GDB and stepped over the m5 commands, they occur only once and in the correct sequence. all

Re: [gem5-users] Double PseudoInst commands while running Parsec

Can you double check with aarch64-linux-gnu-objdump that the binary really only contains a single pseudoop? Maybe it is just an instrumentation bug that doubles it up. I would also recommend that you try to correlate --debug-flags ExecAll or GDB the guest executable around the pseudoop point to na

[gem5-users] Double PseudoInst commands while running Parsec

Hi guys, I'm am running the PARSEC benchmark suite on gem5 ARM in full system simulation mode. For some reason it seems like some m5 PseudoInst (checkpoint, stats_reset, stats_dump) are executed twice and I'm not sure why. I built PARSEC on QEMU following this guide