Ok thanks, I'll try updating my gem5 and see if it works. My gem5 is about 1 month old.
-Trang On Oct 10, 2011, at 4:13 PM, Gabriel Michael Black wrote: > That depends on how old your version of gem5 is. We only recently turned on > O3 by default for X86_FS, and even if you updated your version to the most > recent, if your build directory still has the old settings it won't get built > in. You can change I think the CPU_MODELS variable. I think that's what it's > called, but check scons build/X86_FS/gem5.opt --help. That support is pretty > new and seems to work, but you may run into a bug here and there. > > Gabe > > Quoting Trang Le <trang.le1...@gmail.com>: > >> Hello, >> >> I was running x86 on gem5 and it works fine on non-detail mode. But when I >> tried to run it on detailed mode with PARSEC (canneal) using the following >> command: >> >> build/X86_FS/gem5.opt configs/example/fs.py >> --script=/home/tkl245/gem5/configs/boot/canneal_1c_test.rcS -d --caches >> --l2cache >> >> I get this: >> >> ======================================================================= >> gem5 Simulator System. http://gem5.org >> gem5 is copyrighted software; use the --copyright option for details. >> >> gem5 compiled Sep 13 2011 22:20:51 >> gem5 started Oct 10 2011 14:40:38 >> gem5 executing on camsin1 >> command line: build/X86_FS/gem5.opt configs/example/fs.py >> --script=/home/tkl245/gem5/configs/boot/canneal_1c_test.rcS -d --caches >> --l2cache >> Traceback (most recent call last): >> File "<string>", line 1, in <module> >> File "/home/tkl245/gem5/src/python/m5/main.py", line 356, in main >> exec filecode in scope >> File "configs/example/fs.py", line 107, in <module> >> (TestCPUClass, test_mem_mode, FutureClass) = >> Simulation.setCPUClass(options) >> File "/home/tkl245/gem5/configs/common/Simulation.py", line 49, in >> setCPUClass >> class TmpClass(DerivO3CPU): pass >> NameError: global name 'DerivO3CPU' is not defined >> ========================================================================= >> >> So this makes me wonder if O3 is supported for x86 on gem5 yet? Or maybe I >> am doing something else wrong with PARSEC and it has nothing to do with gem5? >> >> Thanks, >> -Trang >> >> >> _______________________________________________ >> gem5-users mailing list >> gem5-users@gem5.org >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> > > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
