diff options
author | Kevin Ryde <user42@zip.com.au> | 2001-05-03 01:26:16 +0200 |
---|---|---|
committer | Kevin Ryde <user42@zip.com.au> | 2001-05-03 01:26:16 +0200 |
commit | 299e1aec6d288bb636e0f464289a3ab667abad6c (patch) | |
tree | 32e033fb3a71634c6ec9742b8b8f41388945bec2 /tune/time.c | |
parent | f850d327f19635c1825a3c7338c3b8dcedc5568e (diff) | |
download | gmp-299e1aec6d288bb636e0f464289a3ab667abad6c.tar.gz |
Amend a couple of comments.
Diffstat (limited to 'tune/time.c')
-rw-r--r-- | tune/time.c | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/tune/time.c b/tune/time.c index 37e571278..51d198dc0 100644 --- a/tune/time.c +++ b/tune/time.c @@ -42,8 +42,8 @@ MA 02111-1307, USA. gets a default based on the measuring method chosen. speed_cycletime - the time in seconds for each CPU cycle, for example on - a 100 MHz CPU this would be 1.0e-8. This is 0.0 if the CPU frequency is - unknown. + a 100 MHz CPU this would be 1.0e-8. This is 0.0 when uninitialized, or + 1.0 if the CPU frequency couldn't be determined. speed_endtime() and speed_unittime are normally in seconds, but if a @@ -329,7 +329,9 @@ clk_tck (void) /* Assume that if a time difference that's non-zero but less than CLK_TCK/2 - is seen then the routine is microsecond accurate. */ + is seen then the routine is microsecond accurate. + + FIXME: What if clk_tck() is some big value (like 1000000). */ #define MICROSECONDS_P(name, decl, tv, call) \ do { \ |