public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110406] d: Wrong code-gen returning POD structs by value Date: Tue, 27 Jun 2023 08:52:40 +0000 [thread overview] Message-ID: <bug-110406-4-6FZHoxRy7X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110406-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110406 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iains at gcc dot gnu.org --- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> --- If I remember correctly, the underlying issue is that D always has a vtable pointer for a "class" whereas C++ only adds one if needed (i.e. there are actual virtual methods) So we really need to use the 'struct' tag to D for classes without virtual methods that need to interoperate with C++. I think that then D will lay them out without the vtable pointer. We had a fix for this for Darwin - which does not seem to have made upstream just yet. Restesting (there's an unrelated bootstrap regression to work around).
next prev parent reply other threads:[~2023-06-27 8:52 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-26 2:25 [Bug d/110406] New: " ibuclaw at gcc dot gnu.org 2023-06-26 2:33 ` [Bug d/110406] " pinskia at gcc dot gnu.org 2023-06-26 2:44 ` [Bug target/110406] " pinskia at gcc dot gnu.org 2023-06-26 3:06 ` ibuclaw at gcc dot gnu.org 2023-06-26 3:10 ` ibuclaw at gcc dot gnu.org 2023-06-26 4:21 ` pinskia at gcc dot gnu.org 2023-06-26 4:28 ` pinskia at gcc dot gnu.org 2023-06-26 4:32 ` pinskia at gcc dot gnu.org 2023-06-26 9:37 ` ibuclaw at gcc dot gnu.org 2023-06-26 9:38 ` ibuclaw at gcc dot gnu.org 2023-06-26 20:55 ` ibuclaw at gcc dot gnu.org 2023-06-27 8:52 ` iains at gcc dot gnu.org [this message] 2023-06-27 9:27 ` iains at gcc dot gnu.org 2023-06-28 16:33 ` ibuclaw at gcc dot gnu.org 2023-06-28 18:19 ` cvs-commit at gcc dot gnu.org 2023-06-28 18:52 ` cvs-commit at gcc dot gnu.org 2023-06-28 18:55 ` ibuclaw at gcc dot gnu.org
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=bug-110406-4-6FZHoxRy7X@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).