From: Piotr Trojanek <trojanek@adacore.com>
Date: Thu, 8 Sep 2022 12:58:24 +0000 (+0200)
Subject: ada: Only reject volatile ghost objects when SPARK_Mode is On
X-Git-Tag: basepoints/gcc-14~4352
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=5549d2695a36f1cd97a1a5d2089c9c5a7f3fb03b;p=thirdparty%2Fgcc.git

ada: Only reject volatile ghost objects when SPARK_Mode is On

SPARK rule that forbids ghost volatile objects is only affecting proof
and not generation of object code. It is now only applied where SPARK_Mode
is On. This flexibility is needed to compile code automatically instrumented
by GNATcoverage.

gcc/ada/

	* contracts.adb (Analyze_Object_Contract): Check SPARK_Mode before
	applying SPARK rule.
---

diff --git a/gcc/ada/contracts.adb b/gcc/ada/contracts.adb
index 34db67a8cabf..dd573d374c69 100644
--- a/gcc/ada/contracts.adb
+++ b/gcc/ada/contracts.adb
@@ -1207,7 +1207,7 @@ package body Contracts is
          --  A Ghost object cannot be effectively volatile (SPARK RM 6.9(7) and
          --  SPARK RM 6.9(19)).
 
-         elsif Is_Effectively_Volatile (Obj_Id) then
+         elsif SPARK_Mode = On and then Is_Effectively_Volatile (Obj_Id) then
             Error_Msg_N ("ghost object & cannot be volatile", Obj_Id);
 
          --  A Ghost object cannot be imported or exported (SPARK RM 6.9(7)).