From d3a4781ac523adb8bbe17c8ae0aaaf1c06cfe286 Mon Sep 17 00:00:00 2001
From: Nathan Binkert <binkertn@umich.edu>
Date: Mon, 21 Nov 2005 00:22:29 -0500
Subject: 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
---
 python/m5/config.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/python/m5/config.py b/python/m5/config.py
index a954012ea..1e25e0d09 100644
--- a/python/m5/config.py
+++ b/python/m5/config.py
@@ -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)
 
-- 
cgit v1.2.3