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

Actually, you should'nt do math on Clock in the config files.

Browse source 
python/m5/config.py:
    Clock should not be a NumericParamValue since math on it can be
    ambiguous.  (As the comment clearly says.)

--HG--
extra : convert_revision : 74f8ec846c6a980d92e0bf4bf1c7fac73a75b923
This commit is contained in:
Nathan Binkert 2005-11-21 00:22:29 -05:00
parent c4678ece84
commit d3a4781ac5
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
python/m5/config.py
View file

@ -1240,7 +1240,7 @@ class RootClock(ParamValue):
# A generic frequency and/or Latency value. Value is stored as a latency, # A generic frequency and/or Latency value. Value is stored as a latency,
# but to avoid ambiguity this object does not support numeric ops (* or /). # but to avoid ambiguity this object does not support numeric ops (* or /).
# An explicit conversion to a Latency or Frequency must be made first. # An explicit conversion to a Latency or Frequency must be made first.
class Clock(NumericParamValue): class Clock(ParamValue):
def __init__(self, value): def __init__(self, value):
self.value = getLatency(value) self.value = getLatency(value)