I think the pseudo instructions are implemented non-speculative. I think it will stuck at the ROB and wait for all writes to be finished like a memory barrier.
Although the "execution" does not cost cycles, it implies barriers which could slow down the program by various cycles, which depends on the behavior of your program. On Wed, Mar 30, 2016 at 4:53 PM, Abbas Fairouz <[email protected]> wrote: > Hi all, > > How many cycles does M5 pseudo instruction (i.e. dumpstats) does it take > to execute? > > Is it fixed number of cycles for all instructions? > Can we change the number of cycles for specific pseudo instruction? > > -- > > -------------------- > Best regards, > Abbas Fairouz > -------------------- > > _______________________________________________ > 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
