You can add gem5 magic instructions at the start of main to reset the stats and at the end of main to dump the stats. The instructions I remember is like m5_reset and m5_dump or something. Check the magic instruction header file to find the correct format.
On Thu, Nov 10, 2016 at 9:04 AM, Tarcisio Crocomo < [email protected]> wrote: > Hello everyone, > > I have been using gem5 for simulating an ARM CPU and am trying to assess > the impact of adding a tiny amount of instructions to my code (often just > one). This led me to finding out the slightly surprising fact (for me at > least) that in Syscall Emulation mode, passing my executable to gem5 with a > different path (or renaming my executable) affects the number of > instructions simulated. > > For example: > > $GEM5/build/ARM/gem5.opt --outdir=test-sim $GEM5/configs/example/se.py > <options> -c test > > And I have 1371 simulated instructions. By simply doing "mv test test2" I > then end up with 1402 simulated instructions. > > I believe this is the expected behaviour, and gem5 is simulating > everything up to loading the executable, but is there any way I can > eliminate this kind of "noise" (couldn't find a better word) from my > execution? As in, let's say, start counting statistics from a given point > in my executable, "main" for example? > > Thanks in advance, > > Tarcísio > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- yw
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
