Re: Timing Block of GNAT code in milliseconds

[Simon Wright <simon@pushface.org>]

"Steve" <nospam_steved94@comcast.net> writes:

> I tend to think of the Real_Time package as the one to use when you
> are timing events and the Calendar package as the one to use when
> you don't care about precise timing and want the time of day for
> reporting, etc.

It used to be the case with GNAT that there was an amazing similarity
between these two clocks! Looking on 5.02a1, on a first glance it
seems that Real_Time is derived as follows (the first two letters are
the encoding in the distribution, eg if building on NT the file
s-taprop.adb is copied from 5wtaprop.adb).

1s VxWorks/Cert taprop uses tickGet.

56 LynxOS taprop uses clock_gettime.

5a DEC Unix taprop uses clock_gettime.

5f IRIX pthread taprop uses clock_gettime.

5g IRIX athread taprop uses gettimeofday.

5h HP-UX DCE taprop uses clock_gettime.

5i GNU/LinuxThreads taprop uses getttimeofday.

5n Non-tasking taprop returns 0.0.

5o OS/2 taprop uses osprim which is the same as its Clock which is its
system clock.

5p OpenNT, Dec Unix, SCO taprop use osprim which is the same as its
Clock which uses gettimeofday.

5s Solaris taprop uses osprim which is the same as its Clock which
uses gettimeofday.

5v OpenVMS/Alpha taprop uses osprim which is the same as its clock
which uses the system clock.

5w NT taprop uses osprim which uses the performance counter.

5z VxWorks taprop uses clock_gettime.

7s 'POSIX-like' taprop uses clock_gettime.

-- 
Simon Wright                               100% Ada, no bugs.