Try to figure out what instruction is not being destroyed and then why. Maybe some custom insn for your cpu is not implemented properly? On May 4, 2013 4:09 PM, "ignacio charalabidis" <[email protected]> wrote:
> Well, although my copy of gem5 was earlier of the day, I can see this code > in my files as well :/ > > I tried also with debug and before the abortion I see messages like these: > > *0: [sn:1] not destroyed* 1500 times. > > What should I do? If I use smaller intervals (instead of 1M or 10M, 10K > for example) it works fine. > > Thanks, > > > > Date: Sat, 4 May 2013 14:50:47 -0400 > > From: [email protected] > > To: [email protected] > > Subject: Re: [gem5-users] Assertion `instcount <= 1500' failed and > Assertion `!freeList.empty()' when having more than one cpus > > > > 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 > > _______________________________________________ > 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
