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 r14-1759] ada: Fix wrong expansion of limited extension aggregate
Date: Tue, 13 Jun 2023 07:33:34 +0000 (GMT)	[thread overview]
Message-ID: <20230613073334.76EC43858D33@sourceware.org> (raw)

https://gcc.gnu.org/g:ae3fd5e8a75bf7cf18a98b0d0545ade976c1ec05

commit r14-1759-gae3fd5e8a75bf7cf18a98b0d0545ade976c1ec05
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Fri Apr 21 18:30:48 2023 +0200

    ada: Fix wrong expansion of limited extension aggregate
    
    This happens when the ancestor part is itself an aggregate: in this case,
    the tag of the extension aggregate is wrongly set to that of the ancestor.
    
    gcc/ada/
    
            * exp_aggr.adb (Build_Record_Aggr_Code): In the case of an extension
            aggregate of a limited type whose ancestor part is an aggregate, do
            not skip the final code assigning the tag of the extension.

Diff:
---
 gcc/ada/exp_aggr.adb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/gcc/ada/exp_aggr.adb b/gcc/ada/exp_aggr.adb
index c145d79f482..15230571123 100644
--- a/gcc/ada/exp_aggr.adb
+++ b/gcc/ada/exp_aggr.adb
@@ -3039,8 +3039,6 @@ package body Exp_Aggr is
               and then Nkind (Unqualify (Ancestor)) in
                          N_Aggregate | N_Extension_Aggregate
             then
-               Ancestor_Is_Expression := True;
-
                --  Set up finalization data for enclosing record, because
                --  controlled subcomponents of the ancestor part will be
                --  attached to it.

                 reply	other threads:[~2023-06-13  7:33 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=20230613073334.76EC43858D33@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).