public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2055] d: Field names of anonymous delegates should be same as regular delegate types.
Date: Mon, 15 Aug 2022 19:37:28 +0000 (GMT)	[thread overview]
Message-ID: <20220815193728.8015D3858401@sourceware.org> (raw)

https://gcc.gnu.org/g:9fb12ee6fb75be4f980a235dc3f28a29ecc80de0

commit r13-2055-g9fb12ee6fb75be4f980a235dc3f28a29ecc80de0
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Mon Aug 15 09:54:15 2022 +0200

    d: Field names of anonymous delegates should be same as regular delegate types.
    
    Doesn't change anything in the code generation or ABI, but makes it
    consistent with regular delegates as names would match up when
    inspecting tree dumps.
    
    gcc/d/ChangeLog:
    
            * d-codegen.cc (build_delegate_cst): Give anonymous delegate field
            names same as per ABI spec.

Diff:
---
 gcc/d/d-codegen.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/d/d-codegen.cc b/gcc/d/d-codegen.cc
index 3fd4bee58f6..d02da1f81e3 100644
--- a/gcc/d/d-codegen.cc
+++ b/gcc/d/d-codegen.cc
@@ -419,8 +419,8 @@ build_delegate_cst (tree method, tree object, Type *type)
     {
       /* Convert a function method into an anonymous delegate.  */
       ctype = make_struct_type ("delegate()", 2,
-				get_identifier ("object"), TREE_TYPE (object),
-				get_identifier ("func"), TREE_TYPE (method));
+				get_identifier ("ptr"), TREE_TYPE (object),
+				get_identifier ("funcptr"), TREE_TYPE (method));
       TYPE_DELEGATE (ctype) = 1;
     }


                 reply	other threads:[~2022-08-15 19:37 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=20220815193728.8015D3858401@sourceware.org \
    --to=ibuclaw@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).