public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <pmderodat@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-539] [Ada] Fix small glitch in Expand_N_Full_Type_Declaration
Date: Tue, 17 May 2022 08:28:59 +0000 (GMT)	[thread overview]
Message-ID: <20220517082859.693F2385740B@sourceware.org> (raw)

https://gcc.gnu.org/g:42fe7c9a809198b50070eb9033ba2be1447519b9

commit r13-539-g42fe7c9a809198b50070eb9033ba2be1447519b9
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Wed Mar 23 23:47:06 2022 +0100

    [Ada] Fix small glitch in Expand_N_Full_Type_Declaration
    
    The original node is not guaranteed to also be an
    N_Full_Type_Declaration, so the code needs to look into the node itself.
    
    gcc/ada/
    
            * exp_ch3.adb (Expand_N_Full_Type_Declaration): Look into N.

Diff:
---
 gcc/ada/exp_ch3.adb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/gcc/ada/exp_ch3.adb b/gcc/ada/exp_ch3.adb
index f2deff74522..4216fecc438 100644
--- a/gcc/ada/exp_ch3.adb
+++ b/gcc/ada/exp_ch3.adb
@@ -6102,8 +6102,7 @@ package body Exp_Ch3 is
          Par_Id := Base_Type (Full_View (Par_Id));
       end if;
 
-      if Nkind (Type_Definition (Original_Node (N))) =
-                                                   N_Derived_Type_Definition
+      if Nkind (Type_Definition (N)) = N_Derived_Type_Definition
         and then not Is_Tagged_Type (Def_Id)
         and then Present (Freeze_Node (Par_Id))
         and then Present (TSS_Elist (Freeze_Node (Par_Id)))


                 reply	other threads:[~2022-05-17  8:28 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=20220517082859.693F2385740B@sourceware.org \
    --to=pmderodat@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).