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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ae9510073867b651 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-24 12:07:02 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn14feed!wn12feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc52.ops.asp.att.net.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: ANN: GNAT 3.15p binary for OS/2 available References: X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 12.234.13.56 X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc52.ops.asp.att.net 1038168418 12.234.13.56 (Sun, 24 Nov 2002 20:06:58 GMT) NNTP-Posting-Date: Sun, 24 Nov 2002 20:06:58 GMT Organization: AT&T Broadband Date: Sun, 24 Nov 2002 20:07:02 GMT Xref: archiver1.google.com comp.lang.ada:31201 Date: 2002-11-24T20:07:02+00:00 List-Id: If it uses the same run-time library s-osprim.adb and s-taprop.adb, then it has the same bug: Monotonic_Clock isn't monotonic, so a "delay" can be much longer than it should be. I believe moving the line Base_Monotonic_Clock := Base_Clock; from being the last statement in s-osprim.adb, to instead be the last statement in the routine Get_Base_Time, will solve the problem. I sent a bug report to report@gnat.com - is that in general sufficient to inform those who might need to know for non-ACT ports?