It's very likely your benchmark is stalling, and then with nothing more to do, the simulator races to the end of time (the largest number a uint64_t Tick can hold) and dies. Removing the check that fails gracefully at the end of time won't fix the problem, you need to figure out why the simulator runs out of things to do.
Gabe On Thu, Nov 16, 2017 at 6:19 PM, liuchen <[email protected]> wrote: > Hello: > while i was running splash2 Alpha on gem5 alpha se multicore mode,I > always have a "Existing tick 18446744073709551615 simulate() limit reached" > problem. > I changed simulate.cc to shadow the limit_event,but it didn't work,it > will cause core dumped.splash2 i used is from the gem5 website. > Does anyone know what the problem is? > > > > > > _______________________________________________ > 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
