From: Pierre-Marie de Rodat <derodat@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Yannick Moy <moy@adacore.com>
Subject: [Ada] Fix spurious errors on ghost code in generics
Date: Thu, 2 Jun 2022 09:09:01 +0000 [thread overview]
Message-ID: <20220602090901.GA1010764@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
After the recent fix for detecting illegal use of ghost entities in
code, spurious errors could be raised on generic code with ghost, due to
wrong setting of the ghost flags on copied entities from the generic to
the instantiation.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* atree.adb (New_Copy): Reset flags related to ghost entities
before marking the new node.
[-- Attachment #2: patch.diff --]
[-- Type: text/x-diff, Size: 494 bytes --]
diff --git a/gcc/ada/atree.adb b/gcc/ada/atree.adb
--- a/gcc/ada/atree.adb
+++ b/gcc/ada/atree.adb
@@ -1775,6 +1775,11 @@ package body Atree is
-- Mark the copy as Ghost depending on the current Ghost region
+ if Nkind (New_Id) in N_Entity then
+ Set_Is_Checked_Ghost_Entity (New_Id, False);
+ Set_Is_Ignored_Ghost_Entity (New_Id, False);
+ end if;
+
Mark_New_Ghost_Node (New_Id);
New_Node_Debugging_Output (New_Id);
reply other threads:[~2022-06-02 9:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220602090901.GA1010764@adacore.com \
--to=derodat@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=moy@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).