public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw 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: Mon, 26 Jun 2023 09:37:51 +0000	[thread overview]
Message-ID: <bug-110406-4-LSeNm2rax1@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

--- Comment #8 from ibuclaw at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #7)
> (In reply to Andrew Pinski from comment #6)
> > Which itself is GCC 12+ regression too ...
> 
> I filed that as PR 110407, let's see what the x86 backend folks say ...
OK, in the meantime I will proceed with seeing what I did to change the return
behaviour on my end.

So long as C and D agree with each other when it comes to POD types, it almost
doesn't matter to me weather the back-end is following the wrong ABI.

  parent reply	other threads:[~2023-06-26  9:37 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 [this message]
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
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-LSeNm2rax1@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: 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).