Date: Mon, 7 Nov 94 21:42:05 GMT From: dolan AT fnoc DOT navy DOT mil (Kent Dolan) To: dj AT stealth DOT ctron DOT com Subject: Re: clock() problems Cc: djgpp AT sun DOT soe DOT clarkson DOT edu KPD> Well, the PC goes at least to 10 nanosecond resolution, even now. KPD> There are plenty of 100 Mhz '486s out there, so whole nanoseconds KPD> is not such a reach or so far in the future as to be KPD> neglectable. Probably a lot of applications could use profiling KPD> to that resolution even today. DJD> No, I meant that the best resolution of the independent timer DJD> chips available on the PC is around a microsecond (OK; 0.8 DJD> microsecond, but who's counting?) Since there are reliably no DJD> timers with better resolution in a standard PC, there's no point DJD> in reporting any finer resolution. DJD> Perhaps we should set CLOCKS_PER_SEC (or whatever) to 1193046 ? Ah, OK, I'll hush up again for a while. Pretty obviously the clock chips are lagging a long way behind the CPU architectures. Not my area of expertise, obviously. 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: )