From: Bob Duff <duff@adacore.com>
Date: Fri, 12 Jun 2020 13:58:24 +0000 (-0400)
Subject: [Ada] gnatbind: Fix No_Entry_Calls_In_Elaboration_Code message
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=81fcf43389ea53b223e1c16d60b6d8e735e0a4e4;p=gcc.git

[Ada] gnatbind: Fix No_Entry_Calls_In_Elaboration_Code message

gcc/ada/

	* bindo-diagnostics.adb (Output_Invocation_Related_Suggestions):
	Use Cumulative_Restrictions.Set, because Restriction_Active only
	works at compile time.
---

diff --git a/gcc/ada/bindo-diagnostics.adb b/gcc/ada/bindo-diagnostics.adb
index c2ffe447b3f..ed1abf8c377 100644
--- a/gcc/ada/bindo-diagnostics.adb
+++ b/gcc/ada/bindo-diagnostics.adb
@@ -25,7 +25,6 @@
 
 with Binderr;  use Binderr;
 with Debug;    use Debug;
-with Restrict; use Restrict;
 with Rident;   use Rident;
 with Types;    use Types;
 
@@ -1144,7 +1143,7 @@ package body Bindo.Diagnostics is
       --  within the task body on a select or accept statement, eliminating
       --  subsequent invocation edges, thus breaking the cycle.
 
-      if not Restriction_Active (No_Entry_Calls_In_Elaboration_Code)
+      if not Cumulative_Restrictions.Set (No_Entry_Calls_In_Elaboration_Code)
         and then Contains_Task_Activation (G, Cycle)
       then
          Error_Msg_Info