+2019-12-18 Piotr Trojanek <trojanek@adacore.com>
+
+ * doc/gnat_rm/implementation_defined_pragmas.rst,
+ doc/gnat_rm/obsolescent_features.rst,
+ doc/gnat_ugn/gnat_and_program_execution.rst, exp_attr.adb,
+ exp_ch9.adb, init.c, libgnat/s-valrea.adb, par-ch6.adb,
+ sem_attr.adb, sem_ch4.adb, sem_util.ads: Fix trivial typos.
+ * gnat_rm.texi, gnat_ugn.texi: Regenerate.
+
2019-12-18 Gary Dismukes <dismukes@adacore.com>
* sem_res.adb (Resolve_Type_Conversion): Add handling for access
The precondition ensures that one and only one of the case guards is
satisfied on entry to the subprogram.
The postcondition ensures that for the case guard that was True on entry,
-the corrresponding consequence is True on exit. Other consequence expressions
+the corresponding consequence is True on exit. Other consequence expressions
are not evaluated.
A precondition ``P`` and postcondition ``Q`` can also be
The functionality provided by pragma ``Task_Info`` is now part of the
Ada language. The ``CPU`` aspect and the package
``System.Multiprocessors`` offer a less system-dependent way to specify
-task affinity or to query the number of processsors.
+task affinity or to query the number of processors.
Syntax
to this package, though only in cases where it cannot be
sure that ``Long_Long_Integer`` is sufficient to guard against
intermediate overflows. This package does not use dynamic
-alllocation, but it does use the secondary stack, so an
+allocation, but it does use the secondary stack, so an
appropriate secondary stack package must be present (this
is always true for standard full Ada, but may require
specific steps for restricted run times such as ZFP).
Rep_To_Pos_Flag (Ptyp, Loc))))));
else
- -- Add Boolean parameter True, to request program errror if
+ -- Add Boolean parameter True, to request program error if
-- we have a bad representation on our hands. If checks are
-- suppressed, then add False instead
Make_Integer_Literal (Loc, 1))),
Rep_To_Pos_Flag (Ptyp, Loc))))));
else
- -- Add Boolean parameter True, to request program errror if
+ -- Add Boolean parameter True, to request program error if
-- we have a bad representation on our hands. Add False if
-- checks are suppressed.
-- a null trailing statement with the given Loc (which is the sloc of
-- the accept, delay, or entry call statement). There might not be any
-- generated code for the accept, delay, or entry call itself (the effect
- -- of these statements is part of the general processsing done for the
+ -- of these statements is part of the general processing done for the
-- enclosing selective accept, timed entry call, or asynchronous select),
-- and the null statement is there to carry the sloc of that statement to
-- the back-end for trace-based coverage analysis purposes.
The precondition ensures that one and only one of the case guards is
satisfied on entry to the subprogram.
The postcondition ensures that for the case guard that was True on entry,
-the corrresponding consequence is True on exit. Other consequence expressions
+the corresponding consequence is True on exit. Other consequence expressions
are not evaluated.
A precondition @code{P} and postcondition @code{Q} can also be
The functionality provided by pragma @code{Task_Info} is now part of the
Ada language. The @code{CPU} aspect and the package
@code{System.Multiprocessors} offer a less system-dependent way to specify
-task affinity or to query the number of processsors.
+task affinity or to query the number of processors.
Syntax
to this package, though only in cases where it cannot be
sure that @code{Long_Long_Integer} is sufficient to guard against
intermediate overflows. This package does not use dynamic
-alllocation, but it does use the secondary stack, so an
+allocation, but it does use the secondary stack, so an
appropriate secondary stack package must be present (this
is always true for standard full Ada, but may require
specific steps for restricted run times such as ZFP).
operation, drivide by zero, and overflow. This will prevent the VMS runtime
(specifically OTS$CHECK_FP_MODE) from complaining about inconsistent
floating point settings in a mixed language program. Ideally the setting
- would be determined at link time based on setttings in the object files,
+ would be determined at link time based on settings in the object files,
however the VMS linker seems to take the setting from the first object
in the link, e.g. pcrt0.o which is float representation neutral. */
char __gl_float_format = 'I';
if Digit < 0 then
if Digit = Underscore and Index + 1 <= Max then
- -- Underscore is only alllowed if followed by a digit
+ -- Underscore is only allowed if followed by a digit
Digit := As_Digit (Str (Index + 1));
if Digit in Valid_Digit then
Index := Index + 1;
if Pf_Flags.Pbod
- -- Disconnnect this processing if we have scanned a null procedure
+ -- Disconnect this processing if we have scanned a null procedure
-- because in this case the spec is complete anyway with no body.
and then (Nkind (Specification_Node) /= N_Procedure_Specification
-- to a missed warning (the Valid check does not really
-- modify!) If this case, Note will be reset to False.
- -- Skip it as well if the type is an Acccess_To_Constant,
+ -- Skip it as well if the type is an Access_To_Constant,
-- given that no use of the value can modify the prefix.
begin
-- In GNATprove mode we need to preserve the link between
-- the original subtype indication and the anonymous subtype,
- -- to extend proofs to constrained acccess types. We only do
+ -- to extend proofs to constrained access types. We only do
-- that outside of spec expressions, otherwise the declaration
-- cannot be inserted and analyzed. In such a case, GNATprove
-- later rejects the allocator as it is not used here in
function Deepest_Type_Access_Level (Typ : Entity_Id) return Uint;
-- Same as Type_Access_Level, except that if the type is the type of an Ada
-- 2012 stand-alone object of an anonymous access type, then return the
- -- static accesssibility level of the object. In that case, the dynamic
+ -- static accessibility level of the object. In that case, the dynamic
-- accessibility level of the object may take on values in a range. The low
-- bound of that range is returned by Type_Access_Level; this function
-- yields the high bound of that range. Also differs from Type_Access_Level
projects / platform / upstream / gcc.git / commitdiff