X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Andrew Cottrell <andspamtrap DOT aty DOT exemail DOT doty DOT com DOT dot DOT yau AT unknown DOT addr>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Microsoft clock()
Date:	Fri, 09 Jul 2004 18:16:58 +1000
Organization:	HOME
Message-ID:	<7tkse09qsl5m3v51d5rhotn98hnmb80i2n@4ax.com>
References:	<2l4majF8iuhdU1 AT uni-berlin DOT de>
X-Newsreader:	Forte Agent 2.0/32.652
MIME-Version:	1.0
Lines:	22
NNTP-Posting-Host:	220.233.15.233
X-Trace:	1089353122 un-2park-reader-01.sydney.pipenetworks.com.au 31717 220.233.15.233:4712
X-Complaints-To:	Abuse, including message IDs to abuse AT pipenetworks DOT com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

>  detected problematic behavior of clock() on Microsoft Windows.

>============
>Windows 2000
>============
...SNIP....
>So, one can see that gpp and g++ generate quite different "cumulative processor time".
>It seems that "cumulative processor time" generated by g++ (Cygwin) is more believable.

Please goto www.delorie.com and have a look back in time in the DJGPP
workers list and you will find allot of talk about this a few years
ago and what was done to fix it.

In summary:-
1) You did not indicate which version of the DJGPP LIBC you are using.
This makes a BIG difference on 2K.
2) Did you try it on DOS? Does it work, on DOS clock() works.
3) Give the latest DJGPP LIBC a go. Check out the DJGPP newgroup
archive at www.delorie.com for where to find 2.04

Andrew

- Raw text -