Hi all,
I have compiled openmp benchmarks using m5threads. command lines are as follow:
"./build/X86/gem5.opt configs/example/se.py -n 4 -c ../m5threads/tests/test_omp
-o '2 2' --caches --l2cache --l1d_size=128kB --l1i_size=128kB --l2_size=1MB
--l1d_assoc=2 --l1i_assoc=2 --l2_assoc=1
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
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
