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-1679] [Ada] Undo questionable renaming in earlier change Date: Wed, 13 Jul 2022 10:04:43 +0000 (GMT) [thread overview] Message-ID: <20220713100443.BDEEC384F019@sourceware.org> (raw) https://gcc.gnu.org/g:0888e1fea16fa019c424c21989d5bf130f5ec130 commit r13-1679-g0888e1fea16fa019c424c21989d5bf130f5ec130 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Mon Jun 27 17:33:46 2022 +0200 [Ada] Undo questionable renaming in earlier change gcc/ada/ * gcc-interface/decl.cc (gnat_to_gnu_entity) <E_Access_Subtype>: Undo questionable renaming. Diff: --- gcc/ada/gcc-interface/decl.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/ada/gcc-interface/decl.cc b/gcc/ada/gcc-interface/decl.cc index 53c84613e6a..217414312c7 100644 --- a/gcc/ada/gcc-interface/decl.cc +++ b/gcc/ada/gcc-interface/decl.cc @@ -3883,7 +3883,7 @@ gnat_to_gnu_entity (Entity_Id gnat_entity, tree gnu_expr, bool definition) && Is_Frozen (Directly_Designated_Type (gnat_entity)) && No (Freeze_Node (Directly_Designated_Type (gnat_entity)))) { - tree gnu_desig_type + tree gnu_design_base_type = TYPE_IS_FAT_POINTER_P (gnu_type) ? TREE_TYPE (TREE_TYPE (TYPE_FIELDS (gnu_type))) : TREE_TYPE (gnu_type); @@ -3903,7 +3903,7 @@ gnat_to_gnu_entity (Entity_Id gnat_entity, tree gnu_expr, bool definition) /* Otherwise elaborate the designated subtype only if its base type has already been elaborated. */ - else if (!TYPE_IS_DUMMY_P (gnu_desig_type)) + else if (!TYPE_IS_DUMMY_P (gnu_design_base_type)) gnat_to_gnu_entity (Directly_Designated_Type (gnat_entity), NULL_TREE, false); }
reply other threads:[~2022-07-13 10:04 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=20220713100443.BDEEC384F019@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: linkBe 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).