From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8da181ade72859cf
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!wns13feed!worldnet.att.net!attbi_s03.POSTED!53ab2750!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: Re: timeouts
References: <8PKdnU4zIcsjqbPcRVn-rA@megapath.net>
X-Newsreader: Tom's custom newsreader
Message-ID: <nzsXc.315330$a24.276701@attbi_s03>
NNTP-Posting-Host: 24.6.132.82
X-Complaints-To: abuse@comcast.net
X-Trace: attbi_s03 1093555539 24.6.132.82 (Thu, 26 Aug 2004 21:25:39 GMT)
NNTP-Posting-Date: Thu, 26 Aug 2004 21:25:39 GMT
Organization: Comcast Online
Date: Thu, 26 Aug 2004 21:25:40 GMT
Xref: g2news1.google.com comp.lang.ada:3053
Date: 2004-08-26T21:25:40+00:00
List-Id: <comp.lang.ada>

>... QueryPerformanceCounter leaps forward by large amounts. Depending on how
>Ada.Calendar is written, that can have bizarre effects. I believe that Tom
>Moran created a patch for GNAT's Ada.Calendar for that; ...

See the comp.lang.ada thread containing

> Subject: Re: Problems with a TIMER
>
> Date: 2003-01-28 10:42:28 PST
>
> > The target is a processor x86 Family 6 Model 7 Stepping 3 AT/AT COMPATIBLE
> > The results change if I use video-outputs or not (PUT("START TIMER"),
> > PUT("-"), PUT("TIME OUT") are now commented into the code).
> > Why?
>   In what way do the results change?  What compiler, OS, and motherboard
> chip set do you have - see MS Knowledgebase article Q274323.
>   There was a problem with certain chipsets and MS Windows that caused
> the machine clock to appear to jump forward 2**24 ticks (several seconds)
> if you did multiple clock reads with less than several microseconds
> between them.  Gnat 3.15 fixed that, but introduced a new clock error,
> which I reported and they say they've fixed for future versions.  Janus
> has a version with the fix, but I don't know about other compilers.