Well, if you print out the PCState during a loop, you'll see it do something like this:
0=>1 1=>2 2=>3 3=>4 4=>5 and then 5=>0 when the loop finishes... I think. -Griffin On Mon, 19 Dec 2011 20:13:01 +0330, Mahmood Naderan <[email protected]> wrote: > ok thanks. About (0=>1), I read the PCState class in x86/types.hh but > found nothing. > > On 12/19/11, Griffin Wright <[email protected]> wrote: >> >> It represents (PC=>NextPC) for the current instruction. I'm not 100% >> sure >> about 0=>1 but I think it has something to do with loop iterations. >> >> -Griffin Wright >> >> On Mon, 19 Dec 2011 19:58:29 +0330, Mahmood Naderan >> <[email protected]> >> wrote: >>> Hi, >>> In some DPRINTF messages, there is a variable "inst->pcState()" and in >>> the output messages it is shown as >>> >>> (0x405bdd=>0x405be1).(0=>1) >>> >>> What does that mean? >>> >>> -- >>> // Naderan *Mahmood; >>> _______________________________________________ >>> 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 >> _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
