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=-0.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ae9510073867b651 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-25 22:40:03 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeed.vmunix.org!newsfeed01.sul.t-online.de!newsmm00.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail From: DWParsons@T-Online.de (Dave Parsons) Newsgroups: comp.lang.ada Subject: Re: ANN: GNAT 3.15p binary for OS/2 available Date: Tue, 26 Nov 2002 07:37:22 +0100 Organization: T-Online Message-ID: References: Reply-To: DWParsons@T-Online.de Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: news.t-online.com 1038292642 04 14068 FucGE0DbSX-jkk 021126 06:37:22 X-Complaints-To: abuse@t-online.com X-Sender: 0802493406-0001@t-dialin.net User-Agent: ProNews/2 V1.51.ib110 Xref: archiver1.google.com comp.lang.ada:31226 Date: 2002-11-26T07:37:22+01:00 List-Id: On Mon, 25 Nov 2002 08:08:22 UTC, tmoran@acm.org wrote: > > I can only find 'Base_Monotonic_Clock :=3D3D Base_Clock;' in 5wosprim.adb > > which is for NT and not used for OS/2. So, OS/2 would appear at first > > glance not to have that bug > Excellent! The problem lay in attempting to keep the two Windows clocks > in synch, and one monotonically increasing. If one task called Clock, and > that caused a resynch, then Base_Ticks, but not Base_Monotonic_Clock, > would be reset, thus causing a backward movement of Monotonic_Clock, and a > consequent increase in any other task's outstanding "delay"s. Perhaps OS2 > doesn't have such a mess. The symptom was that in a multitasking program > where one task called Clock, and one of the clocks was adjusted manually or > automatically, another task's "delay" would be markedly lengthened. > > do you have a number for the bug report > I just sent it in Saturday. Ok thanks for the explanation. I'll have a look at the OS/2 implementation in a bit more detail to see if it could suffer from a similar problem. Dave