public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/101926] [meta-bug] struct/complex/other argument passing and return should be improved Date: Wed, 12 Jul 2023 21:35:29 +0000 [thread overview] Message-ID: <bug-101926-4-vyiMt32gYV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101926-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101926 Bug 101926 depends on bug 95383, which changed state. Bug 95383 Summary: Poor codegen when constructing a trivial Optional https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95383 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE
next prev parent reply other threads:[~2023-07-12 21:35 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-16 0:53 [Bug middle-end/101926] New: [meta-bug] struct/complex " pinskia at gcc dot gnu.org 2021-08-16 2:13 ` [Bug middle-end/101926] " hjl.tools at gmail dot com 2021-12-19 0:26 ` pinskia at gcc dot gnu.org 2022-02-04 0:50 ` pinskia at gcc dot gnu.org 2022-02-04 0:50 ` pinskia at gcc dot gnu.org 2022-06-10 13:55 ` roger at nextmovesoftware dot com 2022-11-09 15:59 ` pinskia at gcc dot gnu.org 2023-07-01 20:52 ` [Bug middle-end/101926] [meta-bug] struct/complex/other " pinskia at gcc dot gnu.org 2023-07-12 21:35 ` pinskia at gcc dot gnu.org 2023-07-12 21:35 ` pinskia at gcc dot gnu.org [this message] 2023-12-07 19:53 ` rsandifo at gcc dot gnu.org 2024-01-04 0:47 ` guojiufu at gcc dot gnu.org 2024-01-04 1:06 ` guojiufu at gcc dot gnu.org 2024-03-20 6:49 ` pinskia 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-101926-4-vyiMt32gYV@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).