+2018-06-11 Gary Dismukes <dismukes@adacore.com>
+
+ * exp_unst.ads, exp_unst.adb: Typo fixes and minor reformatting.
+
2018-06-11 Hristian Kirtchev <kirtchev@adacore.com>
* exp_ch6.adb (Add_Unconstrained_Actuals_To_Build_In_Place_Call): Do
end if;
end;
- -- For an allocator with a qualified expression, check
- -- type of expression being qualified. The explicit type
- -- name is handled as an entity reference..
+ -- For an allocator with a qualified expression, check type
+ -- of expression being qualified. The explicit type name is
+ -- handled as an entity reference.
if Nkind (N) = N_Allocator
and then Nkind (Expression (N)) = N_Qualified_Expression
Callee := Enclosing_Subprogram (Ent);
if Callee /= Caller
- and then (not Is_Static_Type (Ent)
- or else Needs_Fat_Pointer (Ent))
+ and then (not Is_Static_Type (Ent)
+ or else Needs_Fat_Pointer (Ent))
then
Note_Uplevel_Ref (Ent, N, Caller, Callee);
Comp := Activation_Record_Component (UPJ.Ent);
pragma Assert (Present (Comp));
- -- Do the replacement. If the component type is an
- -- access type, this is an uplevel reference for an
- -- entity that requires a fat pointer, so dereference
- -- the component.
+ -- Do the replacement. If the component type is an access type,
+ -- this is an uplevel reference for an entity that requires a
+ -- fat pointer, so dereference the component.
if Is_Access_Type (Etype (Comp)) then
Rewrite (UPJ.Ref,
-- Objects whose nominal subtype is an unconstrained array type present
-- additional complications for translation into LLVM. The address
- -- attributes of such objects points to the first component of the
+ -- attribute of such objects points to the first component of the
-- array, and the bounds are found elsewhere, typically ahead of the
-- components. In many cases the bounds of an object are stored ahead
-- of the components and can be retrieved from it. However, if the
- -- object is an expression (.e.g a slice) the bounds are not adjacent
+ -- object is an expression (e.g. a slice) the bounds are not adjacent
-- and thus must be conveyed explicitly by means of a so-called
-- fat pointer. This leads to the following enhancements to the
-- handling of uplevel references described so far. This applies only
-- subprograms:
--
-- a) Uplevel references are detected as before during the tree traversal
- -- in Visit_Node. For referenes to uplevel formals, we include those with
- -- an unconstrained array type (e.g. String) even if suvh a type has
+ -- in Visit_Node. For reference to uplevel formals, we include those with
+ -- an unconstrained array type (e.g. String) even if such a type has
-- static bounds.
--
-- b) references to unconstrained formals are recognized in the Subp