changeset 9a469388e8b3 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=9a469388e8b3
description:
config: remove ruby's requirement on the timing cmd line param
Since ruby only works in timing mode, explicitly requiring the timing
cmd line
param to be specified is not necessary.
diffstat:
configs/example/ruby_fs.py | 1 -
configs/example/ruby_se.py | 8 +++-----
2 files changed, 3 insertions(+), 6 deletions(-)
diffs (32 lines):
diff -r d8112aa18a1b -r 9a469388e8b3 configs/example/ruby_fs.py
--- a/configs/example/ruby_fs.py Tue Aug 24 13:20:31 2010 -0700
+++ b/configs/example/ruby_fs.py Tue Aug 24 13:20:32 2010 -0700
@@ -103,7 +103,6 @@
# fast forward with the atomic cpu and instead set the FutureClass to None.
# Therefore the cpus resolve to the correct names and unserialize correctly.
#
-assert(options.timing)
class CPUClass(TimingSimpleCPU): pass
test_mem_mode = 'timing'
FutureClass = None
diff -r d8112aa18a1b -r 9a469388e8b3 configs/example/ruby_se.py
--- a/configs/example/ruby_se.py Tue Aug 24 13:20:31 2010 -0700
+++ b/configs/example/ruby_se.py Tue Aug 24 13:20:32 2010 -0700
@@ -134,14 +134,12 @@
process += [smt_process, ]
smt_idx += 1
-(CPUClass, test_mem_mode, FutureClass) = Simulation.setCPUClass(options)
-
#
# Currently ruby only works in timing mode
#
-assert(options.timing)
-assert(test_mem_mode == 'timing')
-assert(FutureClass == None)
+class CPUClass(TimingSimpleCPU): pass
+test_mem_mode = 'timing'
+FutureClass = None
CPUClass.clock = options.clock
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev
