public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115576] [14/15 regression] Worse code generated for simple struct conversion Date: Fri, 21 Jun 2024 07:52:42 +0000 [thread overview] Message-ID: <bug-115576-4-xI5BXwrp9v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115576-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115576 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2024-06-21 CC| |sayle at gcc dot gnu.org Known to work| |13.3.0 Target Milestone|--- |14.2 Keywords| |missed-optimization, | |needs-bisection Status|UNCONFIRMED |NEW Known to fail| |14.1.0, 15.0 Target|X86_64 |x86_64-*-* Priority|P3 |P2 Summary|[14 regression] Worse code |[14/15 regression] Worse |generated for simple struct |code generated for simple |conversion |struct conversion --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. Probably the TImode enhancements.
next prev parent reply other threads:[~2024-06-21 7:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-21 7:44 [Bug rtl-optimization/115576] New: [14 " jzwinck at gmail dot com 2024-06-21 7:49 ` [Bug c++/115576] " pinskia at gcc dot gnu.org 2024-06-21 7:52 ` rguenth at gcc dot gnu.org [this message] 2024-06-21 17:44 ` [Bug target/115576] [14/15 " pinskia at gcc dot gnu.org 2024-06-25 8:17 ` user202729 at protonmail dot com 2024-06-26 7:10 ` [Bug target/115576] [14/15 regression] Worse code generated for simple struct conversion since r14-2386-gbdf2737cda53a8 user202729 at protonmail dot com
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-115576-4-xI5BXwrp9v@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).