+2018-09-26 Gary Dismukes <dismukes@adacore.com>
+
+ * exp_ch9.adb, layout.adb, sem_attr.adb, sem_res.adb: Fix
+ miscellaneous typos.
+
2018-09-26 Jerome Lambourg <lambourg@adacore.com>
* vxlink.adb: Kill a CodePeer warning.
-- to be E. Bod is either a block or a subprogram body. Used after
-- expanding various kinds of entry bodies into their corresponding
-- constructs. This is needed during unnesting to determine whether a
- -- body geenrated for an entry or an accept alternative includes uplevel
+ -- body generated for an entry or an accept alternative includes uplevel
-- references.
function Trivial_Accept_OK return Boolean;
function Reset_Scope (N : Node_Id) return Traverse_Result;
-- Temporaries may have been declared during expansion of the procedure
-- created for an entry body or an accept alternative. Indicate that
- -- their scope is the new body, to unsure proper generation of uplevel
+ -- their scope is the new body, to ensure proper generation of uplevel
-- references where needed during unnesting.
procedure Reset_Scopes is new Traverse_Proc (Reset_Scope);
-- If unnesting subprograms, subprogram access types contain the
-- address of both the subprogram and an activation record. But if we
-- set that, we'll get a warning on different unchecked conversion
- -- sizes in the RTS. So leave unset ub that case.
+ -- sizes in the RTS. So leave unset in that case.
elsif Unnest_Subprogram_Mode
and then Is_Access_Subprogram_Type (E)
-- The above sets the Scope of the flag entity to the
-- current scope, in which the attribute appears, but
-- the flag declaration has been inserted after that
- -- of Subp_Id, so the scope of the flag the same as
+ -- of Subp_Id, so the scope of the flag is the same as
-- that of Subp_Id. This is relevant when unnesting,
- -- whereh processing depends on correct scope settingl
+ -- where processing depends on correct scope setting.
Set_Scope (Flag_Id, Scop);
end if;
-- (including the body of another expression function) which would
-- place the freeze node in the wrong scope. An expression function
-- is frozen in the usual fashion, by the appearance of a real body,
- -- or at the end of a declarative part. However an implcit call to
+ -- or at the end of a declarative part. However an implicit call to
-- an expression function may appear when it is part of a default
-- expression in a call to an initialiation procedure, and must be
-- frozen now, even if the body is inserted at a later point.