From: Yannick Moy <m...@adacore.com> GNATprove expects the frontend to position correctly range check flags, on expressions which might lead to a range check failure. This was missing on in-out parameters of calls. Now fixed.
There is no impact on compilation. gcc/ada/ * sem_res.adb (Resolve_Actuals): Add range check flag. Tested on x86_64-pc-linux-gnu, committed on master. --- gcc/ada/sem_res.adb | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/gcc/ada/sem_res.adb b/gcc/ada/sem_res.adb index 67062c6b32b..dc48b0b7638 100644 --- a/gcc/ada/sem_res.adb +++ b/gcc/ada/sem_res.adb @@ -4388,6 +4388,17 @@ package body Sem_Res is Resolve (Expression (A)); end if; + -- In GNATprove mode, add a range check flag on scalar + -- conversions for IN OUT parameters. The check may be + -- needed on entry from the call. + + if GNATprove_Mode + and then Ekind (F) = E_In_Out_Parameter + and then Is_Scalar_Type (Etype (F)) + then + Set_Do_Range_Check (Expression (A)); + end if; + -- If the actual is a function call that returns a limited -- unconstrained object that needs finalization, create a -- transient scope for it, so that it can receive the proper -- 2.43.2