+2019-07-03 Bob Duff <duff@adacore.com>
+
+ * einfo.ads, exp_util.adb, layout.ads, sinfo.ads: Spell "laid"
+ correctly.
+
2019-07-03 Ed Schonberg <schonberg@adacore.com>
* sem_ch13.adb (Analyze_Attribute_Definition_Clause): No error
-- Optimize_Alignment_Space (Flag241)
-- Defined in type, subtype, variable, and constant entities. This
--- flag records that the type or object is to be layed out in a manner
+-- flag records that the type or object is to be laid out in a manner
-- consistent with Optimize_Alignment (Space) mode. The compiler and
-- binder ensure a consistent view of any given type or object. If pragma
-- Optimize_Alignment (Off) mode applies to the type/object, then neither
-- Optimize_Alignment_Time (Flag242)
-- Defined in type, subtype, variable, and constant entities. This
--- flag records that the type or object is to be layed out in a manner
+-- flag records that the type or object is to be laid out in a manner
-- consistent with Optimize_Alignment (Time) mode. The compiler and
-- binder ensure a consistent view of any given type or object. If pragma
-- Optimize_Alignment (Off) mode applies to the type/object, then neither
return False;
end if;
- -- Here we have a tagged type, see if it has any unlayed out fields
- -- other than a possible tag and parent fields. If so, we return False.
+ -- Here we have a tagged type, see if it has any component (other than
+ -- tag and parent) with no component_clause. If so, we return False.
Comp := First_Component (U);
while Present (Comp) loop
end if;
end loop;
- -- All components are layed out
+ -- All components have clauses
return True;
end Is_Fully_Repped_Tagged_Type;
-- The following procedures are called from Freeze, so all entities
-- for types and objects that get frozen (which should be all such
- -- entities which are seen by the back end) will get layed out by one
+ -- entities which are seen by the back end) will get laid out by one
-- of these two procedures.
procedure Layout_Type (E : Entity_Id);
-- Einfo.
-- Note: N_Defining_Identifier is an extended node whose fields are
- -- deliberately layed out to match the layout of fields in an ordinary
+ -- deliberately laid out to match the layout of fields in an ordinary
-- N_Identifier node allowing for easy alteration of an identifier
-- node into a defining identifier node. For details, see procedure
-- Sinfo.CN.Change_Identifier_To_Defining_Identifier.
-- in package Einfo.
-- Note: N_Defining_Character_Literal is an extended node whose fields
- -- are deliberate layed out to match the layout of fields in an ordinary
+ -- are deliberate laid out to match the layout of fields in an ordinary
-- N_Character_Literal node allowing for easy alteration of a character
-- literal node into a defining character literal node. For details, see
-- Sinfo.CN.Change_Character_Literal_To_Defining_Character_Literal.
-- in package Einfo.
-- Note: N_Defining_Operator_Symbol is an extended node whose fields
- -- are deliberately layed out to match the layout of fields in an
+ -- are deliberately laid out to match the layout of fields in an
-- ordinary N_Operator_Symbol node allowing for easy alteration of
-- an operator symbol node into a defining operator symbol node.
-- See Sinfo.CN.Change_Operator_Symbol_To_Defining_Operator_Symbol
-- of this node, leaving the N_Selected_Component node used only when
-- the prefix is a record or protected type.
- -- The fields of the N_Expanded_Name node are layed out identically
+ -- The fields of the N_Expanded_Name node are laid out identically
-- to those of the N_Selected_Component node, allowing conversion of
-- an expanded name node to a selected component node to be done
-- easily, see Sinfo.CN.Change_Selected_Component_To_Expanded_Name.