D.8 Monotonic Time
1
[This clause specifies a high-resolution, monotonic
clock package.]
Static Semantics
2
The following language-defined
library package exists:
3
4
type Time
is private;
Time_First :
constant Time;
Time_Last :
constant Time;
Time_Unit :
constant :=
implementation-defined-real-number;
5
type Time_Span
is private;
Time_Span_First :
constant Time_Span;
Time_Span_Last :
constant Time_Span;
Time_Span_Zero :
constant Time_Span;
Time_Span_Unit :
constant Time_Span;
6
Tick :
constant Time_Span;
function Clock
return Time;
7
function "+" (Left : Time; Right : Time_Span) return Time;
function "+" (Left : Time_Span; Right : Time) return Time;
function "-" (Left : Time; Right : Time_Span) return Time;
function "-" (Left : Time; Right : Time) return Time_Span;
8
function "<" (Left, Right : Time) return Boolean;
function "<="(Left, Right : Time) return Boolean;
function ">" (Left, Right : Time) return Boolean;
function ">="(Left, Right : Time) return Boolean;
9
function "+" (Left, Right : Time_Span) return Time_Span;
function "-" (Left, Right : Time_Span) return Time_Span;
function "-" (Right : Time_Span) return Time_Span;
function "*" (Left : Time_Span; Right : Integer) return Time_Span;
function "*" (Left : Integer; Right : Time_Span) return Time_Span;
function "/" (Left, Right : Time_Span) return Integer;
function "/" (Left : Time_Span; Right : Integer) return Time_Span;
10
function "abs"(Right : Time_Span) return Time_Span;
11/1
This paragraph
was deleted.
12
function "<" (Left, Right : Time_Span) return Boolean;
function "<="(Left, Right : Time_Span) return Boolean;
function ">" (Left, Right : Time_Span) return Boolean;
function ">="(Left, Right : Time_Span) return Boolean;
13
function To_Duration (TS : Time_Span)
return Duration;
function To_Time_Span (D : Duration)
return Time_Span;
14/2
{
AI95-00386-01}
function Nanoseconds (NS : Integer)
return Time_Span;
function Microseconds (US : Integer)
return Time_Span;
function Milliseconds (MS : Integer)
return Time_Span;
function Seconds (S : Integer) return Time_Span;
function Minutes (M : Integer) return Time_Span;15
type Seconds_Count
is range implementation-defined;
16
procedure Split(T :
in Time; SC :
out Seconds_Count; TS :
out Time_Span);
function Time_Of(SC : Seconds_Count; TS : Time_Span)
return Time;
17
private
... -- not specified by the language
end Ada.Real_Time;
17.a/2
This paragraph
was deleted.Implementation defined:
Implementation-defined aspects of package
Real_Time.
18
{real time}
In this Annex,
real time is defined to be
the physical time as observed in the external environment. The type Time
is a
time type as defined by
9.6; [values
of this type may be used in a
delay_until_statement.]
Values of this type represent segments of an ideal time line. The set
of values of the type Time corresponds one-to-one with an implementation-defined
range of mathematical integers.
18.a
Discussion: Informally, real time is
defined to be the International Atomic Time (TAI) which is monotonic
and nondecreasing. We use it here for the purpose of discussing rate
of change and monotonic behavior only. It does not imply anything about
the absolute value of Real_Time.Clock, or about Real_Time.Time being
synchronized with TAI. It is also used for real time in the metrics,
for comparison purposes.
18.b
Implementation Note: The specification
of TAI as “real time” does not preclude the use of a simulated
TAI clock for simulated execution environments.
19
{epoch}
{unspecified
[partial]} The Time value I represents the
half-open real time interval that starts with E+I*Time_Unit and is limited
by E+(I+1)*Time_Unit, where Time_Unit is an implementation-defined real
number and E is an unspecified origin point, the
epoch, that is
the same for all values of the type Time. It is not specified by the
language whether the time values are synchronized with any standard time
reference. [For example, E can correspond to the time of system initialization
or it can correspond to the epoch of some time standard.]
19.a
Discussion: E itself does not have to
be a proper time value.
19.b
This half-open interval I consists of all real
numbers R such that E+I*Time_Unit <= R < E+(I+1)*Time_Unit.
20
Values of the type Time_Span represent length of
real time duration. The set of values of this type corresponds one-to-one
with an implementation-defined range of mathematical integers. The Time_Span
value corresponding to the integer I represents the real-time duration
I*Time_Unit.
20.a
Reason: The purpose of this type is similar
to Standard.Duration; the idea is to have a type with a higher resolution.
20.b
Discussion: We looked at many possible
names for this type: Real_Time.Duration, Fine_Duration, Interval, Time_Interval_Length,
Time_Measure, and more. Each of these names had some problems, and we've
finally settled for Time_Span.
21
Time_First and Time_Last are the smallest and largest
values of the Time type, respectively. Similarly, Time_Span_First and
Time_Span_Last are the smallest and largest values of the Time_Span type,
respectively.
22
A value of type Seconds_Count represents an elapsed
time, measured in seconds, since the epoch.
Dynamic Semantics
23
Time_Unit is the smallest amount of real time representable
by the Time type; it is expressed in seconds. Time_Span_Unit is the difference
between two successive values of the Time type. It is also the smallest
positive value of type Time_Span. Time_Unit and Time_Span_Unit represent
the same real time duration.
{clock tick}
A
clock tick is a real time interval during
which the clock value (as observed by calling the Clock function) remains
constant. Tick is the average length of such intervals.
24/2
{
AI95-00432-01}
The function To_Duration converts the value TS to a value of type Duration.
Similarly, the function To_Time_Span converts the value D to a value
of type Time_Span. For
To_Duration both
operations, the result is rounded to the nearest
value
of type Duration exactly representable value
(away from zero if exactly halfway between two
exactly
representable values).
If the result is
outside the range of Duration, Constraint_Error is raised. For To_Time_Span,
the value of D is first rounded to the nearest integral multiple of Time_Unit,
away from zero if exactly halfway between two multiples. If the rounded
value is outside the range of Time_Span, Constraint_Error is raised.
Otherwise, the value is converted to the type Time_Span.25
To_Duration(Time_Span_Zero) returns 0.0, and To_Time_Span(0.0)
returns Time_Span_Zero.
26/2
{
AI95-00386-01}
{
AI95-00432-01}
The functions Nanoseconds, Microseconds,
and Milliseconds
,
Seconds, and Minutes convert the input parameter to a value of
the type Time_Span. NS, US,
and MS
,
S, and M are interpreted as a number of nanoseconds, microseconds,
and milliseconds
, seconds, and minutes
respectively.
The input parameter is first converted
to seconds and rounded to the nearest integral multiple of Time_Unit,
The result is rounded to the nearest exactly
representable value (away from zero if exactly halfway between
two
multiples. If the rounded value is outside
the range of Time_Span, Constraint_Error is raised. Otherwise, the rounded
value is converted to the type Time_Span exactly
representable values).
26.a/2
This paragraph
was deleted.Discussion: {
AI95-00432-01}
The above does not imply that the Time_Span type
will have to accommodate Integer'Last of milliseconds; Constraint_Error
is allowed to be raised.
27
The effects of the operators on Time and Time_Span
are as for the operators defined for integer types.
27.a
Implementation Note: Though time values
are modeled by integers, the types Time and Time_Span need not be implemented
as integers.
28
The function Clock returns the amount of time since
the epoch.
29
The effects of the Split and Time_Of operations are
defined as follows, treating values of type Time, Time_Span, and Seconds_Count
as mathematical integers. The effect of Split(T,SC,TS) is to set SC and
TS to values such that T*Time_Unit = SC*1.0 + TS*Time_Unit, and 0.0 <=
TS*Time_Unit < 1.0. The value returned by Time_Of(SC,TS) is the value
T such that T*Time_Unit = SC*1.0 + TS*Time_Unit.
Implementation Requirements
30
The range of Time values shall be sufficient to uniquely
represent the range of real times from program start-up to 50 years later.
Tick shall be no greater than 1 millisecond. Time_Unit shall be less
than or equal to 20 microseconds.
30.a
Implementation Note: The required range
and accuracy of Time are such that 32-bits worth of seconds and 32-bits
worth of ticks in a second could be used as the representation.
31
Time_Span_First shall be no greater than –3600
seconds, and Time_Span_Last shall be no less than 3600 seconds.
31.a
Reason: This is equivalent to ±
one hour and there is still room for a two-microsecond resolution.
32
{clock jump}
A
clock jump is the difference between two
successive distinct values of the clock (as observed by calling the Clock
function). There shall be no backward clock jumps.
Documentation Requirements
33
The implementation shall document the values of Time_First,
Time_Last, Time_Span_First, Time_Span_Last, Time_Span_Unit, and Tick.
33.a/2
Documentation Requirement:
The values of Time_First, Time_Last,
Time_Span_First, Time_Span_Last, Time_Span_Unit, and Tick for package
Real_Time.
34
The implementation shall document the properties
of the underlying time base used for the clock and for type Time, such
as the range of values supported and any relevant aspects of the underlying
hardware or operating system facilities used.
34.a.1/2
Documentation Requirement:
The properties of the underlying time
base used in package Real_Time.
34.a
Discussion: If there is an underlying
operating system, this might include information about which system call
is used to implement the clock. Otherwise, it might include information
about which hardware clock is used.
35
The implementation shall document whether or not
there is any synchronization with external time references, and if such
synchronization exists, the sources of synchronization information, the
frequency of synchronization, and the synchronization method applied.
35.a.1/2
Documentation Requirement:
Any synchronization of package Real_Time
with external time references.
36/1
The implementation shall document any aspects of
the the external environment that could
interfere with the clock behavior as defined in this clause.
36.a.1/2
Documentation Requirement:
Any aspects of the external environment
that could interfere with package Real_Time.
36.a
Discussion: For example, the implementation
is allowed to rely on the time services of an underlying operating system,
and this operating system clock can implement time zones or allow the
clock to be reset by an operator. This dependence has to be documented.
Metrics
37
For the purpose of the metrics defined in this clause,
real time is defined to be the International Atomic Time (TAI).
38
The implementation
shall document the following metrics:
39
- An upper bound on the real-time duration
of a clock tick. This is a value D such that if t1 and t2 are any real
times such that t1 < t2 and Clockt1
= Clockt2
then t2 – t1 <= D.
40
- An upper bound on the size of a clock
jump.
41
- {drift
rate} An upper bound on the drift rate
of Clock with respect to real time. This is a real number D such that
42
E*(1–D) <= (Clockt+E – Clockt) <= E*(1+D)
provided that: Clockt + E*(1+D) <= Time_Last.
43
- where Clockt
is the value of Clock at time t, and E is a real time duration not less
than 24 hours. The value of E used for this metric shall be reported.
43.a
Reason: This metric is intended to provide
a measurement of the long term (cumulative) deviation; therefore, 24
hours is the lower bound on the measurement period. On some implementations,
this is also the maximum period, since the language does not require
that the range of the type Duration be more than 24 hours. On those implementations
that support longer-range Duration, longer measurements should be performed.
44
- An upper bound on the execution time
of a call to the Clock function, in processor clock cycles.
45
- Upper bounds on the execution times
of the operators of the types Time and Time_Span, in processor clock
cycles.
45.a
Implementation Note: A fast implementation
of the Clock function involves repeated reading until you get the same
value twice. It is highly improbable that more than three reads will
be necessary. Arithmetic on time values should not be significantly slower
than 64-bit arithmetic in the underlying machine instruction set.
45.a.1/2
Documentation Requirement:
The metrics for package Real_Time.
Implementation Permissions
46
Implementations targeted to machines with word size
smaller than 32 bits need not support the full range and granularity
of the Time and Time_Span types.
46.a
Discussion: These requirements are based
on machines with a word size of 32 bits.
46.b
Since the range and granularity are implementation
defined, the supported values need to be documented.
Implementation Advice
47
When appropriate, implementations should provide
configuration mechanisms to change the value of Tick.
47.a.1/2
Implementation Advice:
When appropriate, mechanisms to change
the value of Tick should be provided.
47.a
Reason: This is often needed when the
compilation system was originally targeted to a particular processor
with a particular interval timer, but the customer uses the same processor
with a different interval timer.
47.b
Discussion: Tick is a deferred constant
and not a named number specifically for this purpose.
47.c
Implementation Note: This can be achieved
either by pre-run-time configuration tools, or by having Tick be initialized
(in the package private part) by a function call residing in a board
specific module.
48
It is recommended that Calendar.Clock and Real_Time.Clock
be implemented as transformations of the same time base.
48.a.1/2
Implementation Advice:
Calendar.Clock and Real_Time.Clock should
be transformations of the same time base.
49
It is recommended that the “best” time
base which exists in the underlying system be available to the application
through Clock. “Best” may mean highest accuracy or largest
range.
49.a.1/2
Implementation Advice:
The “best” time base which
exists in the underlying system should be available to the application
through Real_Time.Clock.
50
38 The rules in this clause do not imply
that the implementation can protect the user from operator or installation
errors which could result in the clock being set incorrectly.
51
39 Time_Unit is the granularity of the
Time type. In contrast, Tick represents the granularity of Real_Time.Clock.
There is no requirement that these be the same.
Incompatibilities With Ada 95
51.a/2
{
AI95-00386-01}
{incompatibilities with Ada 95} Functions
Seconds and Minutes are newly added to Real_Time. If Real_Time is referenced
in a use_clause, and an entity E with
a defining_identifier of Seconds or Minutes
is defined in a package that is also referenced in a use_clause,
the entity E may no longer be use-visible, resulting in errors.
This should be rare and is easily fixed if it does occur. Wording Changes from Ada 95
51.b/2
{
AI95-00432-01}
Added wording explaining how and when many of these
functions can raise Constraint_Error. While there always was an intent
to raise Constraint_Error if the values did not fit, there never was
any wording to that effect, and since Time_Span was a private type, the
normal numeric type rules do not apply to it.
Sponsored by Ada-Europe