Hi Milad,
Your simulation is terminating prematurely because of a missing syscall
in gem5's Linux emulation code. I suspect this is happening because you
compiled SPEC with a libc version that is too new for the kernel
emulated by gem5. As far as I know, setitimer (interval timer
configuration) shouldn't be used by bzip2 in unless you've added your
own instrumentation code (or libc is doing something funny).
Looking at the documentation of getitimer & setitimer, it seems like it
would be fairly straight forward to implement them in gem5.
//Andreas
On 08/11/2013 11:57 AM, Milad Mohammadi wrote:
Hi,
I am running gem5 using the command below:
build/X86_SE/gem5.opt $PWD/configs/example/se.py --caches
--l1d_size=32kB --l1i_size=32kB --l2cache --l2_size=256kB
--l3_size=8192kB --clock=2.8GHz -c /path-to-benchmark/401.bzip2 -o
"-kf /path-to-benchmark/bzip2/sample2.ref"
ERROR:
Using Atomic CPU
Global frequency set at 1000000000000 ticks per second
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
**** REAL SIMULATION ****
info: Entering event queue @ 0. Starting simulation...
warn: instruction 'fnstcw_Mw' unimplemented
warn: instruction 'fldcw_Mw' unimplemented
warn: ignoring syscall rt_sigaction(140737488349888, 27, ...)
fatal: syscall setitimer (#38) unimplemented.
@ cycle 4196500
[unimplementedFunc:build/X86_SE/sim/syscall_emul.cc, line 83]
Memory Usage: 651600 KBytes
I am not quite sure what the cause of this error could be.
Any help is greatly appreciated.
Thanks!
-Milad
_______________________________________________
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
