Date: Mon, 7 Nov 94 21:14:40 GMT
From: dolan AT fnoc DOT navy DOT mil (Kent Dolan)
To: dj AT stealth DOT ctron DOT com, dolan AT fnoc DOT navy DOT mil
Subject: Re: clock() problems
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu

KPD> I suspect that timings in nanoseconds might be useful even now, with
KPD> the clock on the TI DSP chip running at order of magnitude 1 GHz, so

DJD> Sigh.  The PC doesn't go that far, and the spec allows the
DJD> implementation to choose the "tic" size according to what it supports.

Well, the PC goes at least to 10 nanosecond resolution, even now. There
are plenty of 100 Mhz '486s out there, so whole nanoseconds is not such
a reach or so far in the future as to be neglectable.  Probably a lot of
applications could use profiling to that resolution even today.

Also, I suspect an awful lot of those TI DSP chips are going _into_
PCs, that being by far the largest installed base to target, so the
Gigahum in in the box, if not on the motherboard (where 60 nanoseconds
seems still to be the state of the art).

Xanthian.
--
Kent, the man from xanth.
Kent Paul Dolan, CSC contractor at Fleet Numerical.  (408) 656-4363.
(Navy Unix email:   )  (Navy cc:Mail email: )  (real world email:     )
<dolan AT fnoc DOT navy DOT mil>  <dolank AT fnoc DOT navy DOT mil>  <xanthian AT well DOT sf DOT ca DOT us>