From: "Marc Poulhiès" <poulhies@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Piotr Trojanek <trojanek@adacore.com>
Subject: [COMMITTED] ada: Simplify detection of the enclosing scope
Date: Tue, 7 May 2024 10:00:33 +0200 [thread overview]
Message-ID: <20240507080033.37876-1-poulhies@adacore.com> (raw)
From: Piotr Trojanek <trojanek@adacore.com>
Code cleanup; behaviour is unaffected.
gcc/ada/
* sem_attr.adb (Analyze_Access_Attribute): Replace loop with
Current_Scope_No_Loops.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/sem_attr.adb | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/gcc/ada/sem_attr.adb b/gcc/ada/sem_attr.adb
index 6140cc0c0d6..e80a144ebb2 100644
--- a/gcc/ada/sem_attr.adb
+++ b/gcc/ada/sem_attr.adb
@@ -988,10 +988,7 @@ package body Sem_Attr is
-- expanded into a loop. Locate scope of type definition,
-- if any.
- Scop := Current_Scope;
- while Ekind (Scop) = E_Loop loop
- Scop := Scope (Scop);
- end loop;
+ Scop := Current_Scope_No_Loops;
-- OK if we are within the scope of a limited type
-- let's mark the component as having per object constraint
--
2.43.2
reply other threads:[~2024-05-07 8:00 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=20240507080033.37876-1-poulhies@adacore.com \
--to=poulhies@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=trojanek@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).