1 ------------------------------------------------------------------------------
3 -- GNAT COMPILER COMPONENTS --
9 -- Copyright (C) 1992-2011, Free Software Foundation, Inc. --
11 -- GNAT is free software; you can redistribute it and/or modify it under --
12 -- terms of the GNU General Public License as published by the Free Soft- --
13 -- ware Foundation; either version 3, or (at your option) any later ver- --
14 -- sion. GNAT is distributed in the hope that it will be useful, but WITH- --
15 -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --
16 -- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License --
17 -- for more details. You should have received a copy of the GNU General --
18 -- Public License distributed with GNAT; see file COPYING3. If not, go to --
19 -- http://www.gnu.org/licenses for a complete copy of the license. --
21 -- GNAT was originally developed by the GNAT team at New York University. --
22 -- Extensive contributions were provided by Ada Core Technologies Inc. --
24 ------------------------------------------------------------------------------
26 -- Package containing utility procedures used throughout the expander
28 with Exp_Tss; use Exp_Tss;
29 with Namet; use Namet;
30 with Rtsfind; use Rtsfind;
31 with Sinfo; use Sinfo;
32 with Types; use Types;
33 with Uintp; use Uintp;
37 -----------------------------------------------
38 -- Handling of Actions Associated with Nodes --
39 -----------------------------------------------
41 -- The evaluation of certain expression nodes involves the elaboration
42 -- of associated types and other declarations, and the execution of
43 -- statement sequences. Expansion routines generating such actions must
44 -- find an appropriate place in the tree to hang the actions so that
45 -- they will be evaluated at the appropriate point.
47 -- Some cases are simple:
49 -- For an expression occurring in a simple statement that is in a list
50 -- of statements, the actions are simply inserted into the list before
51 -- the associated statement.
53 -- For an expression occurring in a declaration (declarations always
54 -- appear in lists), the actions are similarly inserted into the list
55 -- just before the associated declaration.
57 -- The following special cases arise:
59 -- For actions associated with the right operand of a short circuit
60 -- form, the actions are first stored in the short circuit form node
61 -- in the Actions field. The expansion of these forms subsequently
62 -- expands the short circuit forms into if statements which can then
63 -- be moved as described above.
65 -- For actions appearing in the Condition expression of a while loop,
66 -- or an elsif clause, the actions are similarly temporarily stored in
67 -- in the node (N_Elsif_Part or N_Iteration_Scheme) associated with
68 -- the expression using the Condition_Actions field. Subsequently, the
69 -- expansion of these nodes rewrites the control structures involved to
70 -- reposition the actions in normal statement sequence.
72 -- For actions appearing in the then or else expression of a conditional
73 -- expression, these actions are similarly placed in the node, using the
74 -- Then_Actions or Else_Actions field as appropriate. Once again the
75 -- expansion of the N_Conditional_Expression node rewrites the node so
76 -- that the actions can be normally positioned.
78 -- Basically what we do is to climb up to the tree looking for the
79 -- proper insertion point, as described by one of the above cases,
80 -- and then insert the appropriate action or actions.
82 -- Note if more than one insert call is made specifying the same
83 -- Assoc_Node, then the actions are elaborated in the order of the
84 -- calls, and this guarantee is preserved for the special cases above.
86 procedure Insert_Action
87 (Assoc_Node : Node_Id;
88 Ins_Action : Node_Id);
89 -- Insert the action Ins_Action at the appropriate point as described
90 -- above. The action is analyzed using the default checks after it is
91 -- inserted. Assoc_Node is the node with which the action is associated.
93 procedure Insert_Action
94 (Assoc_Node : Node_Id;
97 -- Insert the action Ins_Action at the appropriate point as described
98 -- above. The action is analyzed using the default checks as modified
99 -- by the given Suppress argument after it is inserted. Assoc_Node is
100 -- the node with which the action is associated.
102 procedure Insert_Actions
103 (Assoc_Node : Node_Id;
104 Ins_Actions : List_Id);
105 -- Insert the list of action Ins_Actions at the appropriate point as
106 -- described above. The actions are analyzed using the default checks
107 -- after they are inserted. Assoc_Node is the node with which the actions
108 -- are associated. Ins_Actions may be No_List, in which case the call has
111 procedure Insert_Actions
112 (Assoc_Node : Node_Id;
113 Ins_Actions : List_Id;
114 Suppress : Check_Id);
115 -- Insert the list of action Ins_Actions at the appropriate point as
116 -- described above. The actions are analyzed using the default checks
117 -- as modified by the given Suppress argument after they are inserted.
118 -- Assoc_Node is the node with which the actions are associated.
119 -- Ins_Actions may be No_List, in which case the call has no effect.
121 procedure Insert_Action_After
122 (Assoc_Node : Node_Id;
123 Ins_Action : Node_Id);
124 -- Assoc_Node must be a node in a list. Same as Insert_Action but the
125 -- action will be inserted after N in a manner that is compatible with
126 -- the transient scope mechanism.
128 procedure Insert_Actions_After
129 (Assoc_Node : Node_Id;
130 Ins_Actions : List_Id);
131 -- Assoc_Node must be a node in a list. Same as Insert_Actions but
132 -- actions will be inserted after N in a manner that is compatible with
133 -- the transient scope mechanism. This procedure must be used instead
134 -- of Insert_List_After if Assoc_Node may be in a transient scope.
136 -- Implementation limitation: Assoc_Node must be a statement. We can
137 -- generalize to expressions if there is a need but this is tricky to
138 -- implement because of short-circuits (among other things).???
140 procedure Insert_Library_Level_Action (N : Node_Id);
141 -- This procedure inserts and analyzes the node N as an action at the
142 -- library level for the current unit (i.e. it is attached to the
143 -- Actions field of the N_Compilation_Aux node for the main unit).
145 procedure Insert_Library_Level_Actions (L : List_Id);
146 -- Similar, but inserts a list of actions
148 -----------------------
149 -- Other Subprograms --
150 -----------------------
152 procedure Adjust_Condition (N : Node_Id);
153 -- The node N is an expression whose root-type is Boolean, and which
154 -- represents a boolean value used as a condition (i.e. a True/False
155 -- value). This routine handles the case of C and Fortran convention
156 -- boolean types, which have zero/non-zero semantics rather than the normal
157 -- 0/1 semantics, and also the case of an enumeration rep clause that
158 -- specifies a non-standard representation. On return, node N always has
159 -- the type Standard.Boolean, with a value that is a standard Boolean
160 -- values of 0/1 for False/True. This procedure is used in two situations.
161 -- First, the processing for a condition field always calls
162 -- Adjust_Condition, so that the boolean value presented to the backend is
163 -- a standard value. Second, for the code for boolean operations such as
164 -- AND, Adjust_Condition is called on both operands, and then the operation
165 -- is done in the domain of Standard_Boolean, then Adjust_Result_Type is
166 -- called on the result to possibly reset the original type. This procedure
167 -- also takes care of validity checking if Validity_Checks = Tests.
169 procedure Adjust_Result_Type (N : Node_Id; T : Entity_Id);
170 -- The processing of boolean operations like AND uses the procedure
171 -- Adjust_Condition so that it can operate on Standard.Boolean, which is
172 -- the only boolean type on which the backend needs to be able to implement
173 -- such operators. This means that the result is also of type
174 -- Standard.Boolean. In general the type must be reset back to the original
175 -- type to get proper semantics, and that is the purpose of this procedure.
176 -- N is the node (of type Standard.Boolean), and T is the desired type. As
177 -- an optimization, this procedure leaves the type as Standard.Boolean in
178 -- contexts where this is permissible (in particular for Condition fields,
179 -- and for operands of other logical operations higher up the tree). The
180 -- call to this procedure is completely ignored if the argument N is not of
183 procedure Append_Freeze_Action (T : Entity_Id; N : Node_Id);
184 -- Add a new freeze action for the given type. The freeze action is
185 -- attached to the freeze node for the type. Actions will be elaborated in
186 -- the order in which they are added. Note that the added node is not
187 -- analyzed. The analyze call is found in Exp_Ch13.Expand_N_Freeze_Entity.
189 procedure Append_Freeze_Actions (T : Entity_Id; L : List_Id);
190 -- Adds the given list of freeze actions (declarations or statements) for
191 -- the given type. The freeze actions are attached to the freeze node for
192 -- the type. Actions will be elaborated in the order in which they are
193 -- added, and the actions within the list will be elaborated in list order.
194 -- Note that the added nodes are not analyzed. The analyze call is found in
195 -- Exp_Ch13.Expand_N_Freeze_Entity.
197 procedure Build_Allocate_Deallocate_Proc
199 Is_Allocate : Boolean);
200 -- Create a custom Allocate/Deallocate to be associated with an allocation
203 -- 1) controlled objects
204 -- 2) class-wide objects
205 -- 3) any kind of object on a subpool
207 -- N must be an allocator or the declaration of a temporary variable which
208 -- represents the expression of the original allocator node, otherwise N
209 -- must be a free statement. If flag Is_Allocate is set, the generated
210 -- routine is allocate, deallocate otherwise.
212 function Build_Runtime_Call (Loc : Source_Ptr; RE : RE_Id) return Node_Id;
213 -- Build an N_Procedure_Call_Statement calling the given runtime entity.
214 -- The call has no parameters. The first argument provides the location
215 -- information for the tree and for error messages. The call node is not
216 -- analyzed on return, the caller is responsible for analyzing it.
218 function Build_Task_Image_Decls
222 In_Init_Proc : Boolean := False) return List_Id;
223 -- Build declaration for a variable that holds an identifying string to be
224 -- used as a task name. Id_Ref is an identifier if the task is a variable,
225 -- and a selected or indexed component if the task is component of an
226 -- object. If it is an indexed component, A_Type is the corresponding array
227 -- type. Its index types are used to build the string as an image of the
228 -- index values. For composite types, the result includes two declarations:
229 -- one for a generated function that computes the image without using
230 -- concatenation, and one for the variable that holds the result.
232 -- If In_Init_Proc is true, the call is part of the initialization of
233 -- a component of a composite type, and the enclosing initialization
234 -- procedure must be flagged as using the secondary stack. If In_Init_Proc
235 -- is false, the call is for a stand-alone object, and the generated
236 -- function itself must do its own cleanups.
238 function Component_May_Be_Bit_Aligned (Comp : Entity_Id) return Boolean;
239 -- This function is in charge of detecting record components that may
240 -- cause trouble in the back end if an attempt is made to assign the
241 -- component. The back end can handle such assignments with no problem if
242 -- the components involved are small (64-bits or less) records or scalar
243 -- items (including bit-packed arrays represented with modular types) or
244 -- are both aligned on a byte boundary (starting on a byte boundary, and
245 -- occupying an integral number of bytes).
247 -- However, problems arise for records larger than 64 bits, or for arrays
248 -- (other than bit-packed arrays represented with a modular type) if the
249 -- component starts on a non-byte boundary, or does not occupy an integral
250 -- number of bytes (i.e. there are some bits possibly shared with fields
251 -- at the start or beginning of the component). The back end cannot handle
252 -- loading and storing such components in a single operation.
254 -- This function is used to detect the troublesome situation. it is
255 -- conservative in the sense that it produces True unless it knows for
256 -- sure that the component is safe (as outlined in the first paragraph
257 -- above). The code generation for record and array assignment checks for
258 -- trouble using this function, and if so the assignment is generated
259 -- component-wise, which the back end is required to handle correctly.
261 -- Note that in GNAT 3, the back end will reject such components anyway,
262 -- so the hard work in checking for this case is wasted in GNAT 3, but
263 -- it is harmless, so it is easier to do it in all cases, rather than
264 -- conditionalize it in GNAT 5 or beyond.
266 procedure Convert_To_Actual_Subtype (Exp : Node_Id);
267 -- The Etype of an expression is the nominal type of the expression,
268 -- not the actual subtype. Often these are the same, but not always.
269 -- For example, a reference to a formal of unconstrained type has the
270 -- unconstrained type as its Etype, but the actual subtype is obtained by
271 -- applying the actual bounds. This routine is given an expression, Exp,
272 -- and (if necessary), replaces it using Rewrite, with a conversion to
273 -- the actual subtype, building the actual subtype if necessary. If the
274 -- expression is already of the requested type, then it is unchanged.
276 function Corresponding_Runtime_Package (Typ : Entity_Id) return RTU_Id;
277 -- Return the id of the runtime package that will provide support for
278 -- concurrent type Typ. Currently only protected types are supported,
279 -- and the returned value is one of the following:
280 -- System_Tasking_Protected_Objects
281 -- System_Tasking_Protected_Objects_Entries
282 -- System_Tasking_Protected_Objects_Single_Entry
284 function Current_Sem_Unit_Declarations return List_Id;
285 -- Return the place where it is fine to insert declarations for the
286 -- current semantic unit. If the unit is a package body, return the
287 -- visible declarations of the corresponding spec. For RCI stubs, this
288 -- is necessary because the point at which they are generated may not
289 -- be the earliest point at which they are used.
291 function Duplicate_Subexpr
293 Name_Req : Boolean := False) return Node_Id;
294 -- Given the node for a subexpression, this function makes a logical copy
295 -- of the subexpression, and returns it. This is intended for use when the
296 -- expansion of an expression needs to repeat part of it. For example,
297 -- replacing a**2 by a*a requires two references to a which may be a
298 -- complex subexpression. Duplicate_Subexpr guarantees not to duplicate
299 -- side effects. If necessary, it generates actions to save the expression
300 -- value in a temporary, inserting these actions into the tree using
301 -- Insert_Actions with Exp as the insertion location. The original
302 -- expression and the returned result then become references to this saved
303 -- value. Exp must be analyzed on entry. On return, Exp is analyzed, but
304 -- the caller is responsible for analyzing the returned copy after it is
305 -- attached to the tree. The Name_Req flag is set to ensure that the result
306 -- is suitable for use in a context requiring name (e.g. the prefix of an
307 -- attribute reference).
309 -- Note that if there are any run time checks in Exp, these same checks
310 -- will be duplicated in the returned duplicated expression. The two
311 -- following functions allow this behavior to be modified.
313 function Duplicate_Subexpr_No_Checks
315 Name_Req : Boolean := False) return Node_Id;
316 -- Identical in effect to Duplicate_Subexpr, except that Remove_Checks
317 -- is called on the result, so that the duplicated expression does not
318 -- include checks. This is appropriate for use when Exp, the original
319 -- expression is unconditionally elaborated before the duplicated
320 -- expression, so that there is no need to repeat any checks.
322 function Duplicate_Subexpr_Move_Checks
324 Name_Req : Boolean := False) return Node_Id;
325 -- Identical in effect to Duplicate_Subexpr, except that Remove_Checks is
326 -- called on Exp after the duplication is complete, so that the original
327 -- expression does not include checks. In this case the result returned
328 -- (the duplicated expression) will retain the original checks. This is
329 -- appropriate for use when the duplicated expression is sure to be
330 -- elaborated before the original expression Exp, so that there is no need
331 -- to repeat the checks.
333 procedure Ensure_Defined (Typ : Entity_Id; N : Node_Id);
334 -- This procedure ensures that type referenced by Typ is defined. For the
335 -- case of a type other than an Itype, nothing needs to be done, since
336 -- all such types have declaration nodes. For Itypes, an N_Itype_Reference
337 -- node is generated and inserted at the given node N. This is typically
338 -- used to ensure that an Itype is properly defined outside a conditional
339 -- construct when it is referenced in more than one branch.
341 function Entry_Names_OK return Boolean;
342 -- Determine whether it is appropriate to dynamically allocate strings
343 -- which represent entry [family member] names. These strings are created
344 -- by the compiler and used by GDB.
346 procedure Evolve_And_Then (Cond : in out Node_Id; Cond1 : Node_Id);
347 -- Rewrites Cond with the expression: Cond and then Cond1. If Cond is
348 -- Empty, then simply returns Cond1 (this allows the use of Empty to
349 -- initialize a series of checks evolved by this routine, with a final
350 -- result of Empty indicating that no checks were required). The Sloc field
351 -- of the constructed N_And_Then node is copied from Cond1.
353 procedure Evolve_Or_Else (Cond : in out Node_Id; Cond1 : Node_Id);
354 -- Rewrites Cond with the expression: Cond or else Cond1. If Cond is Empty,
355 -- then simply returns Cond1 (this allows the use of Empty to initialize a
356 -- series of checks evolved by this routine, with a final result of Empty
357 -- indicating that no checks were required). The Sloc field of the
358 -- constructed N_Or_Else node is copied from Cond1.
360 procedure Expand_Subtype_From_Expr
362 Unc_Type : Entity_Id;
363 Subtype_Indic : Node_Id;
365 -- Build a constrained subtype from the initial value in object
366 -- declarations and/or allocations when the type is indefinite (including
369 function Find_Init_Call
371 Rep_Clause : Node_Id) return Node_Id;
372 -- Look for init_proc call for variable Var, either among declarations
373 -- between that of Var and a subsequent Rep_Clause applying to Var, or
374 -- in the list of freeze actions associated with Var, and if found, return
377 function Find_Interface_ADT
379 Iface : Entity_Id) return Elmt_Id;
380 -- Ada 2005 (AI-251): Given a type T implementing the interface Iface,
381 -- return the element of Access_Disp_Table containing the tag of the
384 function Find_Interface_Tag
386 Iface : Entity_Id) return Entity_Id;
387 -- Ada 2005 (AI-251): Given a type T implementing the interface Iface,
388 -- return the record component containing the tag of Iface.
390 function Find_Prim_Op (T : Entity_Id; Name : Name_Id) return Entity_Id;
391 -- Find the first primitive operation of type T whose name is 'Name'.
392 -- This function allows the use of a primitive operation which is not
393 -- directly visible. If T is a class wide type, then the reference is
394 -- to an operation of the corresponding root type. Raises Program_Error
395 -- exception if no primitive operation is found. This is normally an
396 -- internal error, but in some cases is an expected consequence of
397 -- illegalities elsewhere.
399 function Find_Prim_Op
401 Name : TSS_Name_Type) return Entity_Id;
402 -- Find the first primitive operation of type T whose name has the form
403 -- indicated by the name parameter (i.e. is a type support subprogram
404 -- with the indicated suffix). This function allows use of a primitive
405 -- operation which is not directly visible. If T is a class wide type,
406 -- then the reference is to an operation of the corresponding root type.
407 -- Raises Program_Error exception if no primitive operation is found.
408 -- This is normally an internal error, but in some cases is an expected
409 -- consequence of illegalities elsewhere.
411 function Find_Protection_Object (Scop : Entity_Id) return Entity_Id;
412 -- Traverse the scope stack starting from Scop and look for an entry,
413 -- entry family, or a subprogram that has a Protection_Object and return
414 -- it. Raises Program_Error if no such entity is found since the context
415 -- in which this routine is invoked should always have a protection
418 function Find_Protection_Type (Conc_Typ : Entity_Id) return Entity_Id;
419 -- Given a protected type or its corresponding record, find the type of
422 procedure Force_Evaluation
424 Name_Req : Boolean := False);
425 -- Force the evaluation of the expression right away. Similar behavior
426 -- to Remove_Side_Effects when Variable_Ref is set to TRUE. That is to
427 -- say, it removes the side-effects and captures the values of the
428 -- variables. Remove_Side_Effects guarantees that multiple evaluations
429 -- of the same expression won't generate multiple side effects, whereas
430 -- Force_Evaluation further guarantees that all evaluations will yield
433 function Fully_Qualified_Name_String (E : Entity_Id) return String_Id;
434 -- Generates the string literal corresponding to the fully qualified name
435 -- of entity E with an ASCII.NUL appended at the end of the name.
437 procedure Generate_Poll_Call (N : Node_Id);
438 -- If polling is active, then a call to the Poll routine is built,
439 -- and then inserted before the given node N and analyzed.
441 procedure Get_Current_Value_Condition
445 -- This routine processes the Current_Value field of the variable Var. If
446 -- the Current_Value field is null or if it represents a known value, then
447 -- on return Cond is set to N_Empty, and Val is set to Empty.
449 -- The other case is when Current_Value points to an N_If_Statement or an
450 -- N_Elsif_Part or a N_Iteration_Scheme node (see description in Einfo for
451 -- exact details). In this case, Get_Current_Condition digs out the
452 -- condition, and then checks if the condition is known false, known true,
453 -- or not known at all. In the first two cases, Get_Current_Condition will
454 -- return with Op set to the appropriate conditional operator (inverted if
455 -- the condition is known false), and Val set to the constant value. If the
456 -- condition is not known, then Op and Val are set for the empty case
457 -- (N_Empty and Empty).
459 -- The check for whether the condition is true/false unknown depends
462 -- For an IF, the condition is known true in the THEN part, known false
463 -- in any ELSIF or ELSE part, and not known outside the IF statement in
466 -- For an ELSIF, the condition is known true in the ELSIF part, known
467 -- FALSE in any subsequent ELSIF, or ELSE part, and not known before the
468 -- ELSIF, or after the end of the IF statement.
470 -- The caller can use this result to determine the value (for the case of
471 -- N_Op_Eq), or to determine the result of some other test in other cases
472 -- (e.g. no access check required if N_Op_Ne Null).
474 function Get_Stream_Size (E : Entity_Id) return Uint;
475 -- Return the stream size value of the subtype E
477 function Has_Access_Constraint (E : Entity_Id) return Boolean;
478 -- Given object or type E, determine if a discriminant is of an access type
480 function Has_Following_Address_Clause (D : Node_Id) return Boolean;
481 -- D is the node for an object declaration. This function searches the
482 -- current declarative part to look for an address clause for the object
483 -- being declared, and returns True if one is found.
485 function Homonym_Number (Subp : Entity_Id) return Nat;
486 -- Here subp is the entity for a subprogram. This routine returns the
487 -- homonym number used to disambiguate overloaded subprograms in the same
488 -- scope (the number is used as part of constructed names to make sure that
489 -- they are unique). The number is the ordinal position on the Homonym
490 -- chain, counting only entries in the current scope. If an entity is not
491 -- overloaded, the returned number will be one.
493 function Inside_Init_Proc return Boolean;
494 -- Returns True if current scope is within an init proc
496 function In_Library_Level_Package_Body (Id : Entity_Id) return Boolean;
497 -- Given an arbitrary entity, determine whether it appears at the library
498 -- level of a package body.
500 function In_Unconditional_Context (Node : Node_Id) return Boolean;
501 -- Node is the node for a statement or a component of a statement. This
502 -- function determines if the statement appears in a context that is
503 -- unconditionally executed, i.e. it is not within a loop or a conditional
504 -- or a case statement etc.
506 function Is_All_Null_Statements (L : List_Id) return Boolean;
507 -- Return True if all the items of the list are N_Null_Statement nodes.
508 -- False otherwise. True for an empty list. It is an error to call this
509 -- routine with No_List as the argument.
511 function Is_Finalizable_Transient
513 Rel_Node : Node_Id) return Boolean;
514 -- Determine whether declaration Decl denotes a controlled transient which
515 -- should be finalized. Rel_Node is the related context. Even though some
516 -- transient are controlled, they may act as renamings of other objects or
519 function Is_Fully_Repped_Tagged_Type (T : Entity_Id) return Boolean;
520 -- Tests given type T, and returns True if T is a non-discriminated tagged
521 -- type which has a record representation clause that specifies the layout
522 -- of all the components, including recursively components in all parent
523 -- types. We exclude discriminated types for convenience, it is extremely
524 -- unlikely that the special processing associated with the use of this
525 -- routine is useful for the case of a discriminated type, and testing for
526 -- component overlap would be a pain.
528 function Is_Library_Level_Tagged_Type (Typ : Entity_Id) return Boolean;
529 -- Return True if Typ is a library level tagged type. Currently we use
530 -- this information to build statically allocated dispatch tables.
532 function Is_Null_Access_BIP_Func_Call (Expr : Node_Id) return Boolean;
533 -- Determine whether node Expr denotes a build-in-place function call with
534 -- a value of "null" for extra formal BIPaccess.
536 function Is_Non_BIP_Func_Call (Expr : Node_Id) return Boolean;
537 -- Determine whether node Expr denotes a non build-in-place function call
539 function Is_Ref_To_Bit_Packed_Array (N : Node_Id) return Boolean;
540 -- Determine whether the node P is a reference to a bit packed array, i.e.
541 -- whether the designated object is a component of a bit packed array, or a
542 -- subcomponent of such a component. If so, then all subscripts in P are
543 -- evaluated with a call to Force_Evaluation, and True is returned.
544 -- Otherwise False is returned, and P is not affected.
546 function Is_Ref_To_Bit_Packed_Slice (N : Node_Id) return Boolean;
547 -- Determine whether the node P is a reference to a bit packed slice, i.e.
548 -- whether the designated object is bit packed slice or a component of a
549 -- bit packed slice. Return True if so.
551 function Is_Related_To_Func_Return (Id : Entity_Id) return Boolean;
552 -- Determine whether object Id is related to an expanded return statement.
553 -- The case concerned is "return Id.all;".
555 function Is_Possibly_Unaligned_Slice (N : Node_Id) return Boolean;
556 -- Determine whether the node P is a slice of an array where the slice
557 -- result may cause alignment problems because it has an alignment that
558 -- is not compatible with the type. Return True if so.
560 function Is_Possibly_Unaligned_Object (N : Node_Id) return Boolean;
561 -- Node N is an object reference. This function returns True if it is
562 -- possible that the object may not be aligned according to the normal
563 -- default alignment requirement for its type (e.g. if it appears in a
564 -- packed record, or as part of a component that has a component clause.)
566 function Is_Renamed_Object (N : Node_Id) return Boolean;
567 -- Returns True if the node N is a renamed object. An expression is
568 -- considered to be a renamed object if either it is the Name of an object
569 -- renaming declaration, or is the prefix of a name which is a renamed
570 -- object. For example, in:
572 -- x : r renames a (1 .. 2) (1);
574 -- We consider that a (1 .. 2) is a renamed object since it is the prefix
575 -- of the name in the renaming declaration.
577 function Is_Tag_To_CW_Conversion (Obj_Id : Entity_Id) return Boolean;
578 -- Determine whether object Obj_Id is the result of a tag-to-class-wide
581 function Is_Untagged_Derivation (T : Entity_Id) return Boolean;
582 -- Returns true if type T is not tagged and is a derived type,
583 -- or is a private type whose completion is such a type.
585 function Is_Volatile_Reference (N : Node_Id) return Boolean;
586 -- Checks if the node N represents a volatile reference, which can be
587 -- either a direct reference to a variable treated as volatile, or an
588 -- indexed/selected component where the prefix is treated as volatile,
589 -- or has Volatile_Components set. A slice of a volatile variable is
592 function Is_VM_By_Copy_Actual (N : Node_Id) return Boolean;
593 -- Returns True if we are compiling on VM targets and N is a node that
594 -- requires pass-by-copy in these targets.
596 procedure Kill_Dead_Code (N : Node_Id; Warn : Boolean := False);
597 -- N represents a node for a section of code that is known to be dead. Any
598 -- exception handler references and warning messages relating to this code
599 -- are removed. If Warn is True, a warning will be output at the start of N
600 -- indicating the deletion of the code. Note that the tree for the deleted
601 -- code is left intact so that e.g. cross-reference data is still valid.
603 procedure Kill_Dead_Code (L : List_Id; Warn : Boolean := False);
604 -- Like the above procedure, but applies to every element in the given
605 -- list. If Warn is True, a warning will be output at the start of N
606 -- indicating the deletion of the code.
608 function Known_Non_Negative (Opnd : Node_Id) return Boolean;
609 -- Given a node for a subexpression, determines if it represents a value
610 -- that cannot possibly be negative, and if so returns True. A value of
611 -- False means that it is not known if the value is positive or negative.
613 function Known_Non_Null (N : Node_Id) return Boolean;
614 -- Given a node N for a subexpression of an access type, determines if
615 -- this subexpression yields a value that is known at compile time to
616 -- be non-null and returns True if so. Returns False otherwise. It is
617 -- an error to call this function if N is not of an access type.
619 function Known_Null (N : Node_Id) return Boolean;
620 -- Given a node N for a subexpression of an access type, determines if this
621 -- subexpression yields a value that is known at compile time to be null
622 -- and returns True if so. Returns False otherwise. It is an error to call
623 -- this function if N is not of an access type.
625 function Make_Invariant_Call (Expr : Node_Id) return Node_Id;
626 -- Expr is an object of a type which Has_Invariants set (and which thus
627 -- also has an Invariant_Procedure set). If invariants are enabled, this
628 -- function returns a call to the Invariant procedure passing Expr as the
629 -- argument, and returns it unanalyzed. If invariants are not enabled,
630 -- returns a null statement.
632 function Make_Predicate_Call
634 Expr : Node_Id) return Node_Id;
635 -- Typ is a type with Predicate_Function set. This routine builds a call to
636 -- this function passing Expr as the argument, and returns it unanalyzed.
638 function Make_Predicate_Check
640 Expr : Node_Id) return Node_Id;
641 -- Typ is a type with Predicate_Function set. This routine builds a Check
642 -- pragma whose first argument is Predicate, and the second argument is a
643 -- call to the this predicate function with Expr as the argument.
645 function Make_Subtype_From_Expr
647 Unc_Typ : Entity_Id) return Node_Id;
648 -- Returns a subtype indication corresponding to the actual type of an
649 -- expression E. Unc_Typ is an unconstrained array or record, or
652 function May_Generate_Large_Temp (Typ : Entity_Id) return Boolean;
653 -- Determines if the given type, Typ, may require a large temporary of the
654 -- kind that causes back-end trouble if stack checking is enabled. The
655 -- result is True only the size of the type is known at compile time and
656 -- large, where large is defined heuristically by the body of this routine.
657 -- The purpose of this routine is to help avoid generating troublesome
658 -- temporaries that interfere with stack checking mechanism. Note that the
659 -- caller has to check whether stack checking is actually enabled in order
660 -- to guide the expansion (typically of a function call).
662 function Needs_Constant_Address
664 Typ : Entity_Id) return Boolean;
665 -- Check whether the expression in an address clause is restricted to
666 -- consist of constants, when the object has a non-trivial initialization
669 function Needs_Finalization (T : Entity_Id) return Boolean;
670 -- True if type T is controlled, or has controlled subcomponents. Also
671 -- True if T is a class-wide type, because some type extension might add
672 -- controlled subcomponents, except that if pragma Restrictions
673 -- (No_Finalization) applies, this is False for class-wide types.
675 function Non_Limited_Designated_Type (T : Entity_Id) return Entity_Id;
676 -- An anonymous access type may designate a limited view. Check whether
677 -- non-limited view is available during expansion, to examine components
678 -- or other characteristics of the full type.
680 function OK_To_Do_Constant_Replacement (E : Entity_Id) return Boolean;
681 -- This function is used when testing whether or not to replace a reference
682 -- to entity E by a known constant value. Such replacement must be done
683 -- only in a scope known to be safe for such replacements. In particular,
684 -- if we are within a subprogram and the entity E is declared outside the
685 -- subprogram then we cannot do the replacement, since we do not attempt to
686 -- trace subprogram call flow. It is also unsafe to replace statically
687 -- allocated values (since they can be modified outside the scope), and we
688 -- also inhibit replacement of Volatile or aliased objects since their
689 -- address might be captured in a way we do not detect. A value of True is
690 -- returned only if the replacement is safe.
692 function Possible_Bit_Aligned_Component (N : Node_Id) return Boolean;
693 -- This function is used during processing the assignment of a record or
694 -- indexed component. The argument N is either the left hand or right hand
695 -- side of an assignment, and this function determines if there is a record
696 -- component reference where the record may be bit aligned in a manner that
697 -- causes trouble for the back end (see Component_May_Be_Bit_Aligned for
700 procedure Process_Statements_For_Controlled_Objects (N : Node_Id);
701 -- N is a node which contains a non-handled statement list. Inspect the
702 -- statements looking for declarations of controlled objects. If at least
703 -- one such object is found, wrap the statement list in a block.
705 procedure Remove_Side_Effects
707 Name_Req : Boolean := False;
708 Variable_Ref : Boolean := False);
709 -- Given the node for a subexpression, this function replaces the node if
710 -- necessary by an equivalent subexpression that is guaranteed to be side
711 -- effect free. This is done by extracting any actions that could cause
712 -- side effects, and inserting them using Insert_Actions into the tree to
713 -- which Exp is attached. Exp must be analyzed and resolved before the call
714 -- and is analyzed and resolved on return. The Name_Req may only be set to
715 -- True if Exp has the form of a name, and the effect is to guarantee that
716 -- any replacement maintains the form of name. If Variable_Ref is set to
717 -- TRUE, a variable is considered as side effect (used in implementing
718 -- Force_Evaluation). Note: after call to Remove_Side_Effects, it is safe
719 -- to call New_Copy_Tree to obtain a copy of the resulting expression.
721 function Represented_As_Scalar (T : Entity_Id) return Boolean;
722 -- Returns True iff the implementation of this type in code generation
723 -- terms is scalar. This is true for scalars in the Ada sense, and for
724 -- packed arrays which are represented by a scalar (modular) type.
726 function Requires_Cleanup_Actions (N : Node_Id) return Boolean;
727 -- Given a node N, determine whether its declarative and/or statement list
728 -- contains one of the following:
730 -- 1) controlled objects
731 -- 2) library-level tagged types
733 -- The above cases require special actions on scope exit.
735 function Safe_Unchecked_Type_Conversion (Exp : Node_Id) return Boolean;
736 -- Given the node for an N_Unchecked_Type_Conversion, return True if this
737 -- is an unchecked conversion that Gigi can handle directly. Otherwise
738 -- return False if it is one for which the front end must provide a
739 -- temporary. Note that the node need not be analyzed, and thus the Etype
740 -- field may not be set, but in that case it must be the case that the
741 -- Subtype_Mark field of the node is set/analyzed.
743 procedure Set_Current_Value_Condition (Cnode : Node_Id);
744 -- Cnode is N_If_Statement, N_Elsif_Part, or N_Iteration_Scheme (the latter
745 -- when a WHILE condition is present). This call checks whether Condition
746 -- (Cnode) has embedded expressions of a form that should result in setting
747 -- the Current_Value field of one or more entities, and if so sets these
748 -- fields to point to Cnode.
750 procedure Set_Elaboration_Flag (N : Node_Id; Spec_Id : Entity_Id);
751 -- N is the node for a subprogram or generic body, and Spec_Id is the
752 -- entity for the corresponding spec. If an elaboration entity is defined,
753 -- then this procedure generates an assignment statement to set it True,
754 -- immediately after the body is elaborated. However, no assignment is
755 -- generated in the case of library level procedures, since the setting of
756 -- the flag in this case is generated in the binder. We do that so that we
757 -- can detect cases where this is the only elaboration action that is
760 procedure Set_Renamed_Subprogram (N : Node_Id; E : Entity_Id);
761 -- N is an node which is an entity name that represents the name of a
762 -- renamed subprogram. The node is rewritten to be an identifier that
763 -- refers directly to the renamed subprogram, given by entity E.
765 procedure Silly_Boolean_Array_Not_Test (N : Node_Id; T : Entity_Id);
766 -- N is the node for a boolean array NOT operation, and T is the type of
767 -- the array. This routine deals with the silly case where the subtype of
768 -- the boolean array is False..False or True..True, where it is required
769 -- that a Constraint_Error exception be raised (RM 4.5.6(6)).
771 procedure Silly_Boolean_Array_Xor_Test (N : Node_Id; T : Entity_Id);
772 -- N is the node for a boolean array XOR operation, and T is the type of
773 -- the array. This routine deals with the silly case where the subtype of
774 -- the boolean array is True..True, where a raise of a Constraint_Error
775 -- exception is required (RM 4.5.6(6)).
777 function Target_Has_Fixed_Ops
778 (Left_Typ : Entity_Id;
779 Right_Typ : Entity_Id;
780 Result_Typ : Entity_Id) return Boolean;
781 -- Returns True if and only if the target machine has direct support
782 -- for fixed-by-fixed multiplications and divisions for the given
783 -- operand and result types. This is called in package Exp_Fixd to
784 -- determine whether to expand such operations.
786 function Type_May_Have_Bit_Aligned_Components
787 (Typ : Entity_Id) return Boolean;
788 -- Determines if Typ is a composite type that has within it (looking down
789 -- recursively at any subcomponents), a record type which has component
790 -- that may be bit aligned (see Possible_Bit_Aligned_Component). The result
791 -- is conservative, in that a result of False is decisive. A result of True
792 -- means that such a component may or may not be present.
794 procedure Wrap_Cleanup_Procedure (N : Node_Id);
795 -- Given an N_Subprogram_Body node, this procedure adds an Abort_Defer call
796 -- at the start of the statement sequence, and an Abort_Undefer call at the
797 -- end of the statement sequence. All cleanup routines (i.e. those that are
798 -- called from "at end" handlers) must defer abort on entry and undefer
799 -- abort on exit. Note that it is assumed that the code for the procedure
800 -- does not contain any return statements which would allow the flow of
801 -- control to escape doing the undefer call.
804 pragma Inline (Duplicate_Subexpr);
805 pragma Inline (Force_Evaluation);
806 pragma Inline (Is_Library_Level_Tagged_Type);