[Ada] Set_Is_Known_Valid only if Safe_To_Capture_Value
Library-level variables with initializers could have Is_Known_Valid set when analyzing their definition, and the flag would only be cleared when analyzing a statement that assigned to them. Procedures and functions analyzed before the flag got cleared could skip validity checking for the corresponding variable. This patch fixes this problem: we no longer set Is_Known_Valid when analyzing initializers of library-level variables,and use the same Safe_To_Capture_Value predicate that prevents assignments from recording known-valid states. This causes any variable with an initialization value, that would have had its initializer value used as its known constant value if the use is analyzed before any assignment to the variable, to no longer be regarded as holding a constant value. Some might turn out to have a constant value, after all, but we don't know that yet: we can only tell after analyzing every subprogram that could possibly assign to it. At the points where Safe_To_Capture_Value calls are introduced, Never_Set_In_Source does not yet hold its final value. gcc/ada/ * exp_ch3.adb (Expand_N_Object_Declaration): Guard Set_Is_Known_Valid with Safe_To_Capture_Value.
This commit is contained in:
parent
d7ca4dfe8d
commit
2749e4ab8f
@ -7534,6 +7534,7 @@ package body Exp_Ch3 is
|
||||
elsif Comes_From_Source (N)
|
||||
and then Is_Discrete_Type (Typ)
|
||||
and then Expr_Known_Valid (Expr)
|
||||
and then Safe_To_Capture_Value (N, Def_Id)
|
||||
then
|
||||
Set_Is_Known_Valid (Def_Id);
|
||||
|
||||
@ -7564,7 +7565,9 @@ package body Exp_Ch3 is
|
||||
and then not Is_Generic_Type (Etype (Def_Id))
|
||||
then
|
||||
Ensure_Valid (Expr);
|
||||
Set_Is_Known_Valid (Def_Id);
|
||||
if Safe_To_Capture_Value (N, Def_Id) then
|
||||
Set_Is_Known_Valid (Def_Id);
|
||||
end if;
|
||||
end if;
|
||||
end if;
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user