public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: "Marc Poulhiès" <dkm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2927] ada: Fix checking of Refined_State with nested package renamings
Date: Thu, 29 Sep 2022 09:09:20 +0000 (GMT)	[thread overview]
Message-ID: <20220929090920.161CE3858287@sourceware.org> (raw)

https://gcc.gnu.org/g:01ea0437ead0dda3acd51cfb80a01de5feb56929

commit r13-2927-g01ea0437ead0dda3acd51cfb80a01de5feb56929
Author: Piotr Trojanek <trojanek@adacore.com>
Date:   Fri Sep 23 19:06:54 2022 +0200

    ada: Fix checking of Refined_State with nested package renamings
    
    When collecting package state declared in package body, we should only
    recursively examine the visible part of nested packages while ignoring other
    entities related to packages (e.g. package bodies or package renamings).
    
    gcc/ada/
    
            * sem_util.adb (Collect_Visible_States): Ignore package renamings.

Diff:
---
 gcc/ada/sem_util.adb | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gcc/ada/sem_util.adb b/gcc/ada/sem_util.adb
index 9ae082ca2e1..25e886e1ca1 100644
--- a/gcc/ada/sem_util.adb
+++ b/gcc/ada/sem_util.adb
@@ -6018,8 +6018,11 @@ package body Sem_Util is
                Append_New_Elmt (Item_Id, States);
 
             --  Recursively gather the visible states of a nested package
+            --  except for nested package renamings.
 
-            elsif Ekind (Item_Id) = E_Package then
+            elsif Ekind (Item_Id) = E_Package
+              and then No (Renamed_Entity (Item_Id))
+            then
                Collect_Visible_States (Item_Id, States);
             end if;

                 reply	other threads:[~2022-09-29  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=20220929090920.161CE3858287@sourceware.org \
    --to=dkm@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).