1 ------------------------------------------------------------------------------
3 -- GNAT COMPILER COMPONENTS --
9 -- Copyright (C) 1992-2005 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 2, 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 COPYING. If not, write --
19 -- to the Free Software Foundation, 51 Franklin Street, Fifth Floor, --
20 -- Boston, MA 02110-1301, USA. --
22 -- GNAT was originally developed by the GNAT team at New York University. --
23 -- Extensive contributions were provided by Ada Core Technologies Inc. --
25 ------------------------------------------------------------------------------
27 -- Package containing routines used to deal with runtime checks. These
28 -- routines are used both by the semantics and by the expander. In some
29 -- cases, checks are enabled simply by setting flags for gigi, and in
30 -- other cases the code for the check is expanded.
32 -- The approach used for range and length checks, in regards to suppressed
33 -- checks, is to attempt to detect at compilation time that a constraint
34 -- error will occur. If this is detected a warning or error is issued and the
35 -- offending expression or statement replaced with a constraint error node.
36 -- This always occurs whether checks are suppressed or not. Dynamic range
37 -- checks are, of course, not inserted if checks are suppressed.
39 with Types; use Types;
40 with Uintp; use Uintp;
45 -- Called for each new main source program, to initialize internal
46 -- variables used in the package body of the Checks unit.
48 function Access_Checks_Suppressed (E : Entity_Id) return Boolean;
49 function Accessibility_Checks_Suppressed (E : Entity_Id) return Boolean;
50 function Discriminant_Checks_Suppressed (E : Entity_Id) return Boolean;
51 function Division_Checks_Suppressed (E : Entity_Id) return Boolean;
52 function Elaboration_Checks_Suppressed (E : Entity_Id) return Boolean;
53 function Index_Checks_Suppressed (E : Entity_Id) return Boolean;
54 function Length_Checks_Suppressed (E : Entity_Id) return Boolean;
55 function Overflow_Checks_Suppressed (E : Entity_Id) return Boolean;
56 function Range_Checks_Suppressed (E : Entity_Id) return Boolean;
57 function Storage_Checks_Suppressed (E : Entity_Id) return Boolean;
58 function Tag_Checks_Suppressed (E : Entity_Id) return Boolean;
59 -- These functions check to see if the named check is suppressed,
60 -- either by an active scope suppress setting, or because the check
61 -- has been specifically suppressed for the given entity. If no entity
62 -- is relevant for the current check, then Empty is used as an argument.
63 -- Note: the reason we insist on specifying Empty is to force the
64 -- caller to think about whether there is any relevant entity that
67 -- General note on following checks. These checks are always active if
68 -- Expander_Active and not Inside_A_Generic. They are inactive and have
69 -- no effect Inside_A_Generic. In the case where not Expander_Active
70 -- and not Inside_A_Generic, most of them are inactive, but some of them
71 -- operate anyway since they may generate useful compile time warnings.
73 procedure Apply_Access_Check (N : Node_Id);
74 -- Determines whether an expression node requires a runtime access
75 -- check and if so inserts the appropriate run-time check.
77 procedure Apply_Accessibility_Check (N : Node_Id; Typ : Entity_Id);
78 -- Given a name N denoting an access parameter, emits a run-time
79 -- accessibility check (if necessary), checking that the level of
80 -- the object denoted by the access parameter is not deeper than the
81 -- level of the type Typ. Program_Error is raised if the check fails.
83 procedure Apply_Alignment_Check (E : Entity_Id; N : Node_Id);
84 -- E is the entity for an object. If there is an address clause for
85 -- this entity, and checks are enabled, then this procedure generates
86 -- a check that the specified address has an alignment consistent with
87 -- the alignment of the object, raising PE if this is not the case. The
88 -- resulting check (if one is generated) is inserted before node N.
90 procedure Apply_Array_Size_Check (N : Node_Id; Typ : Entity_Id);
91 -- N is the node for an object declaration that declares an object of
92 -- array type Typ. This routine generates, if necessary, a check that
93 -- the size of the array is not too large, raising Storage_Error if so.
95 procedure Apply_Arithmetic_Overflow_Check (N : Node_Id);
96 -- Given a binary arithmetic operator (+ - *) expand a software integer
97 -- overflow check using range checks on a larger checking type or a call
98 -- to an appropriate runtime routine. This is used for all three operators
99 -- for the signed integer case, and for +/- in the fixed-point case. The
100 -- check is expanded only if Software_Overflow_Checking is enabled and
101 -- Do_Overflow_Check is set on node N. Note that divide is handled
102 -- separately using Apply_Arithmetic_Divide_Overflow_Check.
104 procedure Apply_Constraint_Check
107 No_Sliding : Boolean := False);
108 -- Top-level procedure, calls all the others depending on the class of Typ.
109 -- Checks that expression N verifies the constraint of type Typ. No_Sliding
110 -- is only relevant for constrained array types, id set to true, it
111 -- checks that indexes are in range.
113 procedure Apply_Discriminant_Check
116 Lhs : Node_Id := Empty);
117 -- Given an expression N of a discriminated type, or of an access type
118 -- whose designated type is a discriminanted type, generates a check to
119 -- ensure that the expression can be converted to the subtype given as
120 -- the second parameter. Lhs is empty except in the case of assignments,
121 -- where the target object may be needed to determine the subtype to
122 -- check against (such as the cases of unconstrained formal parameters
123 -- and unconstrained aliased objects). For the case of unconstrained
124 -- formals, the check is peformed only if the corresponding actual is
125 -- constrained, i.e., whether Lhs'Constrained is True.
127 function Build_Discriminant_Checks
131 -- Subsidiary routine for Apply_Discriminant_Check. Builds the expression
132 -- that compares discriminants of the expression with discriminants of the
133 -- type. Also used directly for membership tests (see Exp_Ch4.Expand_N_In).
135 procedure Apply_Divide_Check (N : Node_Id);
136 -- The node kind is N_Op_Divide, N_Op_Mod, or N_Op_Rem. An appropriate
137 -- check is generated to ensure that the right operand is non-zero. In
138 -- the divide case, we also check that we do not have the annoying case
139 -- of the largest negative number divided by minus one.
141 procedure Apply_Type_Conversion_Checks (N : Node_Id);
142 -- N is an N_Type_Conversion node. A type conversion actually involves
143 -- two sorts of checks. The first check is the checks that ensures that
144 -- the operand in the type conversion fits onto the base type of the
145 -- subtype it is being converted to (see RM 4.6 (28)-(50)). The second
146 -- check is there to ensure that once the operand has been converted to
147 -- a value of the target type, this converted value meets the
148 -- constraints imposed by the target subtype (see RM 4.6 (51)).
150 procedure Apply_Universal_Integer_Attribute_Checks (N : Node_Id);
151 -- The argument N is an attribute reference node intended for processing
152 -- by gigi. The attribute is one that returns a universal integer, but
153 -- the attribute reference node is currently typed with the expected
154 -- result type. This routine deals with range and overflow checks needed
155 -- to make sure that the universal result is in range.
157 procedure Determine_Range
162 -- N is a node for a subexpression. If N is of a discrete type with no
163 -- error indications, and no other peculiarities (e.g. missing type
164 -- fields), then OK is True on return, and Lo and Hi are set to a
165 -- conservative estimate of the possible range of values of N. Thus if OK
166 -- is True on return, the value of the subexpression N is known to like in
167 -- the range Lo .. Hi (inclusive). If the expression is not of a discrete
168 -- type, or some kind of error condition is detected, then OK is False on
169 -- exit, and Lo/Hi are set to No_Uint. Thus the significance of OK being
170 -- False on return is that no useful information is available on the range
171 -- of the expression.
173 procedure Install_Null_Excluding_Check (N : Node_Id);
174 -- Determines whether an access node requires a runtime access check and
175 -- if so inserts the appropriate run-time check.
177 -------------------------------------------------------
178 -- Control and Optimization of Range/Overflow Checks --
179 -------------------------------------------------------
181 -- Range checks are controlled by the Do_Range_Check flag. The front end
182 -- is responsible for setting this flag in relevant nodes. Originally
183 -- the back end generated all corresponding range checks. But later on
184 -- we decided to generate all range checks in the front end. We are now
185 -- in the transitional phase where some of these checks are still done
186 -- by the back end, but many are done by the front end.
188 -- Overflow checks are similarly controlled by the Do_Overflow_Check flag.
189 -- The difference here is that if Backend_Overflow_Checks is is
190 -- (Backend_Overflow_Checks_On_Target set False), then the actual overflow
191 -- checks are generated by the front end, but if back end overflow checks
192 -- are active (Backend_Overflow_Checks_On_Target set True), then the back
193 -- end does generate the checks.
195 -- The following two routines are used to set these flags, they allow
196 -- for the possibility of eliminating checks. Checks can be eliminated
197 -- if an identical check has already been performed.
199 procedure Enable_Overflow_Check (N : Node_Id);
200 -- First this routine determines if an overflow check is needed by doing
201 -- an appropriate range check. If a check is not needed, then the call
202 -- has no effect. If a check is needed then this routine sets the flag
203 -- Set Do_Overflow_Check in node N to True, unless it can be determined
204 -- that the check is not needed. The only condition under which this is
205 -- the case is if there was an identical check earlier on.
207 procedure Enable_Range_Check (N : Node_Id);
208 -- Set Do_Range_Check flag in node N True, unless it can be determined
209 -- that the check is not needed. The only condition under which this is
210 -- the case is if there was an identical check earlier on. This routine
211 -- is not responsible for doing range analysis to determine whether or
212 -- not such a check is needed -- the caller is expected to do this. The
213 -- one other case in which the request to set the flag is ignored is
214 -- when Kill_Range_Check is set in an N_Unchecked_Conversion node.
216 -- The following routines are used to keep track of processing sequences
217 -- of statements (e.g. the THEN statements of an IF statement). A check
218 -- that appears within such a sequence can eliminate an identical check
219 -- within this sequence of statements. However, after the end of the
220 -- sequence of statements, such a check is no longer of interest, since
221 -- it may not have been executed.
223 procedure Conditional_Statements_Begin;
224 -- This call marks the start of processing of a sequence of statements.
225 -- Every call to this procedure must be followed by a matching call to
226 -- Conditional_Statements_End.
228 procedure Conditional_Statements_End;
229 -- This call removes from consideration all saved checks since the
230 -- corresponding call to Conditional_Statements_Begin. These two
231 -- procedures operate in a stack like manner.
233 -- The mechanism for optimizing checks works by remembering checks
234 -- that have already been made, but certain conditions, for example
235 -- an assignment to a variable involved in a check, may mean that the
236 -- remembered check is no longer valid, in the sense that if the same
237 -- expression appears again, another check is required because the
238 -- value may have changed.
240 -- The following routines are used to note conditions which may render
241 -- some or all of the stored and remembered checks to be invalidated.
243 procedure Kill_Checks (V : Entity_Id);
244 -- This procedure records an assignment or other condition that causes
245 -- the value of the variable to be changed, invalidating any stored
246 -- checks that reference the value. Note that all such checks must
247 -- be discarded, even if they are not in the current statement range.
249 procedure Kill_All_Checks;
250 -- This procedure kills all remembered checks
252 -----------------------------
253 -- Length and Range Checks --
254 -----------------------------
256 -- In the following procedures, there are three arguments which have
257 -- a common meaning as follows:
259 -- Expr The expression to be checked. If a check is required,
260 -- the appropriate flag will be placed on this node. Whether
261 -- this node is further examined depends on the setting of
262 -- the parameter Source_Typ, as described below.
264 -- Target_Typ The target type on which the check is to be based. For
265 -- example, if we have a scalar range check, then the check
266 -- is that we are in range of this type.
268 -- Source_Typ Normally Empty, but can be set to a type, in which case
269 -- this type is used for the check, see below.
271 -- The checks operate in one of two modes:
273 -- If Source_Typ is Empty, then the node Expr is examined, at the very
274 -- least to get the source subtype. In addition for some of the checks,
275 -- the actual form of the node may be examined. For example, a node of
276 -- type Integer whose actual form is an Integer conversion from a type
277 -- with range 0 .. 3 can be determined to have a value in range 0 .. 3.
279 -- If Source_Typ is given, then nothing can be assumed about the Expr,
280 -- and indeed its contents are not examined. In this case the check is
281 -- based on the assumption that Expr can be an arbitrary value of the
284 -- Currently, the only case in which a Source_Typ is explicitly supplied
285 -- is for the case of Out and In_Out parameters, where, for the conversion
286 -- on return (the Out direction), the types must be reversed. This is
287 -- handled by the caller.
289 procedure Apply_Length_Check
291 Target_Typ : Entity_Id;
292 Source_Typ : Entity_Id := Empty);
293 -- This procedure builds a sequence of declarations to do a length check
294 -- that checks if the lengths of the two arrays Target_Typ and source type
295 -- are the same. The resulting actions are inserted at Node using a call
296 -- to Insert_Actions.
298 -- For access types, the Directly_Designated_Type is retrieved and
299 -- processing continues as enumerated above, with a guard against null
302 -- Note: calls to Apply_Length_Check currently never supply an explicit
303 -- Source_Typ parameter, but Apply_Length_Check takes this parameter and
304 -- processes it as described above for consistency with the other routines
307 procedure Apply_Range_Check
309 Target_Typ : Entity_Id;
310 Source_Typ : Entity_Id := Empty);
311 -- For an Node of kind N_Range, constructs a range check action that tests
312 -- first that the range is not null and then that the range is contained in
313 -- the Target_Typ range.
315 -- For scalar types, constructs a range check action that first tests that
316 -- the expression is contained in the Target_Typ range. The difference
317 -- between this and Apply_Scalar_Range_Check is that the latter generates
318 -- the actual checking code in gigi against the Etype of the expression.
320 -- For constrained array types, construct series of range check actions
321 -- to check that each Expr range is properly contained in the range of
324 -- For a type conversion to an unconstrained array type, constructs a range
325 -- check action to check that the bounds of the source type are within the
326 -- constraints imposed by the Target_Typ.
328 -- For access types, the Directly_Designated_Type is retrieved and
329 -- processing continues as enumerated above, with a guard against null
332 -- The source type is used by type conversions to unconstrained array
333 -- types to retrieve the corresponding bounds.
335 procedure Apply_Static_Length_Check
337 Target_Typ : Entity_Id;
338 Source_Typ : Entity_Id := Empty);
339 -- Tries to determine statically whether the two array types source type
340 -- and Target_Typ have the same length. If it can be determined at compile
341 -- time that they do not, then an N_Raise_Constraint_Error node replaces
342 -- Expr, and a warning message is issued.
344 procedure Apply_Scalar_Range_Check
346 Target_Typ : Entity_Id;
347 Source_Typ : Entity_Id := Empty;
348 Fixed_Int : Boolean := False);
349 -- For scalar types, determines whether an expression node should be
350 -- flagged as needing a runtime range check. If the node requires such a
351 -- check, the Do_Range_Check flag is turned on. The Fixed_Int flag if set
352 -- causes any fixed-point values to be treated as though they were discrete
353 -- values (i.e. the underlying integer value is used).
355 type Check_Result is private;
356 -- Type used to return result of Range_Check call, for later use in
357 -- call to Insert_Range_Checks procedure.
359 procedure Append_Range_Checks
360 (Checks : Check_Result;
362 Suppress_Typ : Entity_Id;
363 Static_Sloc : Source_Ptr;
364 Flag_Node : Node_Id);
365 -- Called to append range checks as returned by a call to Range_Check.
366 -- Stmts is a list to which either the dynamic check is appended or the
367 -- raise Constraint_Error statement is appended (for static checks).
368 -- Static_Sloc is the Sloc at which the raise CE node points, Flag_Node is
369 -- used as the node at which to set the Has_Dynamic_Check flag. Checks_On
370 -- is a boolean value that says if range and index checking is on or not.
372 procedure Insert_Range_Checks
373 (Checks : Check_Result;
375 Suppress_Typ : Entity_Id;
376 Static_Sloc : Source_Ptr := No_Location;
377 Flag_Node : Node_Id := Empty;
378 Do_Before : Boolean := False);
379 -- Called to insert range checks as returned by a call to Range_Check.
380 -- Node is the node after which either the dynamic check is inserted or
381 -- the raise Constraint_Error statement is inserted (for static checks).
382 -- Suppress_Typ is the type to check to determine if checks are suppressed.
383 -- Static_Sloc, if passed, is the Sloc at which the raise CE node points,
384 -- otherwise Sloc (Node) is used. The Has_Dynamic_Check flag is normally
385 -- set at Node. If Flag_Node is present, then this is used instead as the
386 -- node at which to set the Has_Dynamic_Check flag. Normally the check is
387 -- inserted after, if Do_Before is True, the check is inserted before
392 Target_Typ : Entity_Id;
393 Source_Typ : Entity_Id := Empty;
394 Warn_Node : Node_Id := Empty)
396 -- Like Apply_Range_Check, except it does not modify anything. Instead
397 -- it returns an encapsulated result of the check operations for later
398 -- use in a call to Insert_Range_Checks. If Warn_Node is non-empty, its
399 -- Sloc is used, in the static case, for the generated warning or error.
400 -- Additionally, it is used rather than Expr (or Low/High_Bound of Expr)
401 -- in constructing the check.
403 -----------------------
404 -- Expander Routines --
405 -----------------------
407 -- Some of the earlier processing for checks results in temporarily setting
408 -- the Do_Range_Check flag rather than actually generating checks. Now we
409 -- are moving the generation of such checks into the front end for reasons
410 -- of efficiency and simplicity (there were difficutlies in handling this
411 -- in the back end when side effects were present in the expressions being
414 -- Probably we could eliminate the Do_Range_Check flag entirely and
415 -- generate the checks earlier, but this is a delicate area and it
416 -- seemed safer to implement the following routines, which are called
417 -- late on in the expansion process. They check the Do_Range_Check flag
418 -- and if it is set, generate the actual checks and reset the flag.
420 procedure Generate_Range_Check
422 Target_Type : Entity_Id;
423 Reason : RT_Exception_Code);
424 -- This procedure is called to actually generate and insert a range check.
425 -- A check is generated to ensure that the value of N lies within the range
426 -- of the target type. Note that the base type of N may be different from
427 -- the base type of the target type. This happens in the conversion case.
428 -- The Reason parameter is the exception code to be used for the exception
431 -- Note on the relation of this routine to the Do_Range_Check flag. Mostly
432 -- for historical reasons, we often set the Do_Range_Check flag and then
433 -- later we call Generate_Range_Check if this flag is set. Most probably we
434 -- could eliminate this intermediate setting of the flag (historically the
435 -- back end dealt with range checks, using this flag to indicate if a check
436 -- was required, then we moved checks into the front end).
438 procedure Generate_Index_Checks (N : Node_Id);
439 -- This procedure is called to generate index checks on the subscripts for
440 -- the indexed component node N. Each subscript expression is examined, and
441 -- if the Do_Range_Check flag is set, an appropriate index check is
442 -- generated and the flag is reset.
444 -- Similarly, we set the flag Do_Discriminant_Check in the semantic
445 -- analysis to indicate that a discriminant check is required for selected
446 -- component of a discriminated type. The following routine is called from
447 -- the expander to actually generate the call.
449 procedure Generate_Discriminant_Check (N : Node_Id);
450 -- N is a selected component for which a discriminant check is required to
451 -- make sure that the discriminants have appropriate values for the
452 -- selection. This is done by calling the appropriate discriminant checking
453 -- routine for the selector.
455 -----------------------
456 -- Validity Checking --
457 -----------------------
459 -- In (RM 13.9.1(9-11)) we have the following rules on invalid values
461 -- If the representation of a scalar object does not represent value of
462 -- the object's subtype (perhaps because the object was not initialized),
463 -- the object is said to have an invalid representation. It is a bounded
464 -- error to evaluate the value of such an object. If the error is
465 -- detected, either Constraint_Error or Program_Error is raised.
466 -- Otherwise, execution continues using the invalid representation. The
467 -- rules of the language outside this subclause assume that all objects
468 -- have valid representations. The semantics of operations on invalid
469 -- representations are as follows:
471 -- 10 If the representation of the object represents a value of the
472 -- object's type, the value of the type is used.
474 -- 11 If the representation of the object does not represent a value
475 -- of the object's type, the semantics of operations on such
476 -- representations is implementation-defined, but does not by
477 -- itself lead to erroneous or unpredictable execution, or to
478 -- other objects becoming abnormal.
480 -- We quote the rules in full here since they are quite delicate. Most
481 -- of the time, we can just compute away with wrong values, and get a
482 -- possibly wrong result, which is well within the range of allowed
483 -- implementation defined behavior. The two tricky cases are subscripted
484 -- array assignments, where we don't want to do wild stores, and case
485 -- statements where we don't want to do wild jumps.
487 -- In GNAT, we control validity checking with a switch -gnatV that can take
488 -- three parameters, n/d/f for None/Default/Full. These modes have the
489 -- following meanings:
491 -- None (no validity checking)
493 -- In this mode, there is no specific checking for invalid values
494 -- and the code generator assumes that all stored values are always
495 -- within the bounds of the object subtype. The consequences are as
498 -- For case statements, an out of range invalid value will cause
499 -- Constraint_Error to be raised, or an arbitrary one of the case
500 -- alternatives will be executed. Wild jumps cannot result even
501 -- in this mode, since we always do a range check
503 -- For subscripted array assignments, wild stores will result in
504 -- the expected manner when addresses are calculated using values
505 -- of subscripts that are out of range.
507 -- It could perhaps be argued that this mode is still conformant with
508 -- the letter of the RM, since implementation defined is a rather
509 -- broad category, but certainly it is not in the spirit of the
510 -- RM requirement, since wild stores certainly seem to be a case of
511 -- erroneous behavior.
513 -- Default (default standard RM-compatible validity checking)
515 -- In this mode, which is the default, minimal validity checking is
516 -- performed to ensure no erroneous behavior as follows:
518 -- For case statements, an out of range invalid value will cause
519 -- Constraint_Error to be raised.
521 -- For subscripted array assignments, invalid out of range
522 -- subscript values will cause Constraint_Error to be raised.
524 -- Full (Full validity checking)
526 -- In this mode, the protections guaranteed by the standard mode are
527 -- in place, and the following additional checks are made:
529 -- For every assignment, the right side is checked for validity
531 -- For every call, IN and IN OUT parameters are checked for validity
533 -- For every subscripted array reference, both for stores and loads,
534 -- all subscripts are checked for validity.
536 -- These checks are not required by the RM, but will in practice
537 -- improve the detection of uninitialized variables, particularly
538 -- if used in conjunction with pragma Normalize_Scalars.
540 -- In the above description, we talk about performing validity checks,
541 -- but we don't actually generate a check in a case where the compiler
542 -- can be sure that the value is valid. Note that this assurance must
543 -- be achieved without assuming that any uninitialized value lies within
544 -- the range of its type. The following are cases in which values are
545 -- known to be valid. The flag Is_Known_Valid is used to keep track of
546 -- some of these cases.
548 -- If all possible stored values are valid, then any uninitialized
549 -- value must be valid.
551 -- Literals, including enumeration literals, are clearly always valid
553 -- Constants are always assumed valid, with a validity check being
554 -- performed on the initializing value where necessary to ensure that
557 -- For variables, the status is set to known valid if there is an
558 -- initializing expression. Again a check is made on the initializing
559 -- value if necessary to ensure that this assumption is valid. The
560 -- status can change as a result of local assignments to a variable.
561 -- If a known valid value is unconditionally assigned, then we mark
562 -- the left side as known valid. If a value is assigned that is not
563 -- known to be valid, then we mark the left side as invalid. This
564 -- kind of processing does NOT apply to non-local variables since we
565 -- are not following the flow graph (more properly the flow of actual
566 -- processing only corresponds to the flow graph for local assignments).
567 -- For non-local variables, we preserve the current setting, i.e. a
568 -- validity check is performed when assigning to a knonwn valid global.
570 -- Note: no validity checking is required if range checks are suppressed
571 -- regardless of the setting of the validity checking mode.
573 -- The following procedures are used in handling validity checking
575 procedure Apply_Subscript_Validity_Checks (Expr : Node_Id);
576 -- Expr is the node for an indexed component. If validity checking and
577 -- range checking are enabled, all subscripts for this indexed component
578 -- are checked for validity.
580 procedure Check_Valid_Lvalue_Subscripts (Expr : Node_Id);
581 -- Expr is a lvalue, i.e. an expression representing the target of an
582 -- assignment. This procedure checks for this expression involving an
583 -- assignment to an array value. We have to be sure that all the subscripts
584 -- in such a case are valid, since according to the rules in (RM
585 -- 13.9.1(9-11)) such assignments are not permitted to result in erroneous
586 -- behavior in the case of invalid subscript values.
588 procedure Ensure_Valid (Expr : Node_Id; Holes_OK : Boolean := False);
589 -- Ensure that Expr represents a valid value of its type. If this type
590 -- is not a scalar type, then the call has no effect, since validity
591 -- is only an issue for scalar types. The effect of this call is to
592 -- check if the value is known valid, if so, nothing needs to be done.
593 -- If this is not known, then either Expr is set to be range checked,
594 -- or specific checking code is inserted so that an exception is raised
595 -- if the value is not valid.
597 -- The optional argument Holes_OK indicates whether it is necessary to
598 -- worry about enumeration types with non-standard representations leading
599 -- to "holes" in the range of possible representations. If Holes_OK is
600 -- True, then such values are assumed valid (this is used when the caller
601 -- will make a separate check for this case anyway). If Holes_OK is False,
602 -- then this case is checked, and code is inserted to ensure that Expr is
603 -- valid, raising Constraint_Error if the value is not valid.
605 function Expr_Known_Valid (Expr : Node_Id) return Boolean;
606 -- This function tests it the value of Expr is known to be valid in the
607 -- sense of RM 13.9.1(9-11). In the case of GNAT, it is only discrete types
608 -- which are a concern, since for non-discrete types we simply continue
609 -- computation with invalid values, which does not lead to erroneous
610 -- behavior. Thus Expr_Known_Valid always returns True if the type of Expr
611 -- is non-discrete. For discrete types the value returned is True only if
612 -- it can be determined that the value is Valid. Otherwise False is
615 procedure Insert_Valid_Check (Expr : Node_Id);
616 -- Inserts code that will check for the value of Expr being valid, in
617 -- the sense of the 'Valid attribute returning True. Constraint_Error
618 -- will be raised if the value is not valid.
620 procedure Null_Exclusion_Static_Checks (N : Node_Id);
621 -- Ada 2005 (AI-231): Check bad usages of the null-exclusion issue
623 procedure Remove_Checks (Expr : Node_Id);
624 -- Remove all checks from Expr except those that are only executed
625 -- conditionally (on the right side of And Then/Or Else. This call
626 -- removes only embedded checks (Do_Range_Check, Do_Overflow_Check).
630 type Check_Result is array (Positive range 1 .. 2) of Node_Id;
631 -- There are two cases for the result returned by Range_Check:
633 -- For the static case the result is one or two nodes that should cause
634 -- a Constraint_Error. Typically these will include Expr itself or the
635 -- direct descendents of Expr, such as Low/High_Bound (Expr)). It is the
636 -- responsibility of the caller to rewrite and substitute the nodes with
637 -- N_Raise_Constraint_Error nodes.
639 -- For the non-static case a single N_Raise_Constraint_Error node with a
640 -- non-empty Condition field is returned.
642 -- Unused entries in Check_Result, if any, are simply set to Empty For
643 -- external clients, the required processing on this result is achieved
644 -- using the Insert_Range_Checks routine.
646 pragma Inline (Apply_Length_Check);
647 pragma Inline (Apply_Range_Check);
648 pragma Inline (Apply_Static_Length_Check);
OSDN Git Service
