This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: (libf2c) libu77 SYSTEM_CLOCK win32 support.
- To: N8TM at aol dot com
- Subject: Re: (libf2c) libu77 SYSTEM_CLOCK win32 support.
- From: craig at jcb-sc dot com
- Date: 16 Apr 1999 15:20:06 -0000
- Cc: khan at xraylith dot wisc dot edu, egcs-patches at egcs dot cygnus dot com
- Cc: craig at jcb-sc dot com
- References: <6acac349.24482c95@aol.com>
>In a message dated 4/15/99 9:30:46 PM Pacific Daylight Time,
>khan@xraylith.wisc.EDU writes:
>
>> + if (cnt > (unsigned long) (INT_MAX))
>> + *count = INT_MAX; /* also dubious */
>
>I'd prefer to let it run on into negative values, which can be checked for by
>the receiver and adjusted if desired. I'd also prefer to have higher
>resolution than 1 msec, without of course going to a timer which overflows in
>a matter of minutes. I wouldn't expect people to use SYSTEM_CLOCK() to
>measure uptime, but you know better than I.
Working clocks tick. And most of them overflow in one way or another,
at some time or another.
So, I agree, I'd rather not have SYSTEM_CLOCK changed to stop ticking.
It's already documented (or should be) to have overflow problems on
some systems.
tq vm, (burley)