What CPU? I hit this assertion with x86 FS and found it was due to some missing code and submitted a patch: http://reviews.gem5.org/r/1828/
The problem was fixed already for ARM. The assertion does not necessarily have to do with instructions executed by your benchmark.. I would guess the freeList empty problem is related. Commenting out assertions is not usually the right way to fix things. :) You might like to use gem5.debug to gather more information about what is breaking. On Sat, May 4, 2013 at 1:07 PM, ignacio charalabidis <[email protected]> wrote: > Hello, > > I was able to run all my benchmarks for whatever number of instructions and > intervals I had chosen so far, for each core separately. > > Now, I am using more than one cores and the following assertions happen: > > Assertion `instcount <= 1500' failed > > I read somewhere that I can comment it out. I did and then this assertion is > raised: > > Assertion `!freeList.empty()' failed > > Why that happen? If I use less instructions this does not happen, but I want > to perform the previous ones. > Any hint on that? > > I am running using gem5.opt. > > > > > > _______________________________________________ > 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
