From: Yannick Moy Date: Tue, 9 Jul 2019 07:54:14 +0000 (+0000) Subject: [Ada] Sinfo: refine comment for Do_Range_Check X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=ff606db0166573fee17f6d81895f7d882fd15169;p=gcc.git [Ada] Sinfo: refine comment for Do_Range_Check 2019-07-09 Yannick Moy gcc/ada/ * sinfo.ads: Refine comment for Do_Range_Check. From-SVN: r273277 --- diff --git a/gcc/ada/ChangeLog b/gcc/ada/ChangeLog index 948d0fa30d1..17c27abcfd5 100644 --- a/gcc/ada/ChangeLog +++ b/gcc/ada/ChangeLog @@ -1,3 +1,7 @@ +2019-07-09 Yannick Moy + + * sinfo.ads: Refine comment for Do_Range_Check. + 2019-07-09 Yannick Moy * exp_spark.adb (Expand_SPARK_N_Attribute_Reference): Expand diff --git a/gcc/ada/sinfo.ads b/gcc/ada/sinfo.ads index b1e57bfda3b..7be56cb9850 100644 --- a/gcc/ada/sinfo.ads +++ b/gcc/ada/sinfo.ads @@ -754,7 +754,11 @@ package Sinfo is -- GNATprove mode. As a special case, the front end does not insert a -- Do_Division_Check flag on float exponentiation expressions, for the case -- where the value is 0.0 and the exponent is negative, although this case - -- does lead to a division check failure. + -- does lead to a division check failure. As another special case, + -- the frontend does not insert a Do_Range_Check on an allocator where + -- the designated type is scalar, and the designated type is more + -- constrained than the type of the initialized allocator value or the type + -- of the default value for an uninitialized allocator. -- Note: the expander always takes care of the Do_Range check case, -- so this flag will never be set in the expanded tree passed to the