sanchayanmaity/gem5
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

config: remove ruby's requirement on the timing cmd line param

Browse source 
Since ruby only works in timing mode, explicitly requiring the timing cmd line
param to be specified is not necessary.
This commit is contained in:
Brad Beckmann 2010-08-24 13:20:32 -07:00
parent 8572d8fd91
commit 0e610290d0
2 changed files with 3 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
configs/example/ruby_fs.py
View file

@ -103,7 +103,6 @@ else:
# fast forward with the atomic cpu and instead set the FutureClass to None. # fast forward with the atomic cpu and instead set the FutureClass to None.
# Therefore the cpus resolve to the correct names and unserialize correctly. # Therefore the cpus resolve to the correct names and unserialize correctly.
# #
assert(options.timing)
class CPUClass(TimingSimpleCPU): pass class CPUClass(TimingSimpleCPU): pass
test_mem_mode = 'timing' test_mem_mode = 'timing'
FutureClass = None FutureClass = None

8
configs/example/ruby_se.py
View file

@ -134,14 +134,12 @@ if options.detailed:
process += [smt_process, ] process += [smt_process, ]
smt_idx += 1 smt_idx += 1
(CPUClass, test_mem_mode, FutureClass) = Simulation.setCPUClass(options)
# #
# Currently ruby only works in timing mode # Currently ruby only works in timing mode
# #
assert(options.timing) class CPUClass(TimingSimpleCPU): pass
assert(test_mem_mode == 'timing') test_mem_mode = 'timing'
assert(FutureClass == None) FutureClass = None
CPUClass.clock = options.clock CPUClass.clock = options.clock