Date: Mon, 7 Nov 94 13:34:39 -0500
From: dj AT stealth DOT ctron DOT com (DJ Delorie)
To: dolan AT fnoc DOT navy DOT mil
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: clock() problems

> Probably it is more than time for the "powers that be" to confess that
> 32 bits is no longer sufficient time resolution when gate speeds are
> in femtoseconds and time since the epoch is in decades.
> 
> A good start would be a structure of two thirty-two bit longs, with the
> binary seconds point between them.

gcc supports "long long", which is 64 bits.  If we scale that to
microseconds, it's good for about 584942 years.  Is it worth the
performance penalty?