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, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,8c564a80b820db35 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.224.230 with SMTP id rf6mr13654452pbc.4.1330978655798; Mon, 05 Mar 2012 12:17:35 -0800 (PST) Path: h9ni43224pbe.0!nntp.google.com!news2.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Any leap year issues caused by Ada yesterday? Date: Mon, 5 Mar 2012 21:17:34 +0100 Organization: cbb software GmbH Message-ID: References: <4f4f746a$0$6565$9b4e6d93@newsspool3.arcor-online.net> <20608866.730.1330963171058.JavaMail.geo-discussion-forums@ynbq18> <1t8v4akrmapkl.1xwfi9yxtw2ji$.dlg@40tude.net> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: /bBpnkeEm9kG1v1C1CjDFw.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Date: 2012-03-05T21:17:34+01:00 List-Id: On Mon, 05 Mar 2012 18:30:46 +0000, Simon Wright wrote: > "Dmitry A. Kazakov" writes: > >> BTW, I would not wonder to see Real_Time.Time and Calendar.Time same >> or correlated. > > We were surprised and disappointed to find that earlier releases of GNAT > did have them the same. What happens to your precise timing if you get > an NTP update in the middle of it? Nothing, because I would expect the NTP client to leave alone the clock readings and the arithmetic of. It should rather adjust Split and Time_Of. In our setups we are using a different schema anyway. Instead of adjusting clocks we do the time stamps when sending them from host to host. > OK, this is slightly GNAT-related, since (at that time, anyway) "delay > 0.5" translated under the hood into "delay until now + 0.5" on VxWorks, Yes, but NTP should not mingle in that. [I don't know how the VxWorks NTP client works.] > so you were always related to the actual clock. VxWorks clock on i7 is a garbage. It is driven by the timer interrupts, i.e. to get 1ms resolution you need 1000 interrupts per second. We keep on asking Wind River to fix the mess, but without much success so far. GNAT simply uses that clock. So delay 0.001 may mean absolutely anything under VxWorks. To fix that one should rewrite the time driver. > AdaCore accepted the bug report (after we pointed out the "shall" in > ARM95 D.8(32)). Well, I would not blame AdaCore for that, it is Wind River's fault, IMO. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de