From: "Marc Poulhiès" <poulhies@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Piotr Trojanek <trojanek@adacore.com>
Subject: [COMMITTED] ada: Recognize iterated_component_association as potentially unevaluated
Date: Tue, 13 Jun 2023 09:38:37 +0200 [thread overview]
Message-ID: <20230613073837.240516-1-poulhies@adacore.com> (raw)
From: Piotr Trojanek <trojanek@adacore.com>
Routine Is_Potentially_Unevaluated was written for Ada 2012, but now we
use it for Ada 2022 as well, so it must recognize iterated component
associations (which were added by Ada 2022) as an array component
association.
gcc/ada/
* sem_util.adb (Is_Potentially_Unevaluated): Recognize iterated
component association as potentially unevaluated.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/sem_util.adb | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/gcc/ada/sem_util.adb b/gcc/ada/sem_util.adb
index b82978ba99e..23668f1bec5 100644
--- a/gcc/ada/sem_util.adb
+++ b/gcc/ada/sem_util.adb
@@ -19566,7 +19566,8 @@ package body Sem_Util is
elsif Nkind (Par) = N_Quantified_Expression then
return Expr = Condition (Par);
- elsif Nkind (Par) = N_Component_Association
+ elsif Nkind (Par) in N_Component_Association
+ | N_Iterated_Component_Association
and then Expr = Expression (Par)
and then Nkind (Parent (Par))
in N_Aggregate | N_Delta_Aggregate | N_Extension_Aggregate
@@ -19708,10 +19709,15 @@ package body Sem_Util is
then
return True;
- -- For component associations continue climbing; it may be part of
- -- an array aggregate.
+ -- For component associations continue climbing; it may be part of an
+ -- array aggregate. For iterated component association we know that
+ -- it belongs to an array aggreate, but only its expression is
+ -- potentially unevaluated, not discrete choice list or iterator
+ -- specification.
- elsif Nkind (Par) = N_Component_Association then
+ elsif Nkind (Par) in N_Component_Association
+ | N_Iterated_Component_Association
+ then
null;
-- If the context is not an expression, or if is the result of
--
2.40.0
reply other threads:[~2023-06-13 7:38 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=20230613073837.240516-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).