delorie.com/archives/browse.cgi | search |
From: | "Anthony.Appleyard" <MCLSSAA2 AT fs2 DOT mt DOT umist DOT ac DOT uk> |
Organization: | Materials Science Centre |
To: | djgpp AT delorie DOT com |
Date: | Mon, 21 Jul 1997 09:44:22 GMT-1 |
Subject: | Re: Standard tiiming func's & O3+ cause odd errors |
Reply-to: | Anthony DOT Appleyard AT umist DOT ac DOT uk |
Message-ID: | <5AD5E65CCE@fs2.mt.umist.ac.uk> |
Nate Eldredge <eldredge AT ap DOT net> wrote:- > Although CLOCKS_PER_SEC claims to be about 1000000, in reality the 55 ms > timer ticks are just scaled to produce the clock() output, leading to big > jumps. ... Oh indeed!?!?!?! Then how genuinely can a Gnu C/C++ program time a process to the nearest microsecond or so???
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |