Actually, you should'nt do math on Clock in the config files.
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:
parent
c4678ece84
commit
d3a4781ac5
1 changed files with 1 additions and 1 deletions
|
@ -1240,7 +1240,7 @@ class RootClock(ParamValue):
|
|||
# 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 /).
|
||||
# An explicit conversion to a Latency or Frequency must be made first.
|
||||
class Clock(NumericParamValue):
|
||||
class Clock(ParamValue):
|
||||
def __init__(self, value):
|
||||
self.value = getLatency(value)
|
||||
|
||||
|
|
Loading…
Reference in a new issue