public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "user202729 at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115576] [14/15 regression] Worse code generated for simple struct conversion Date: Tue, 25 Jun 2024 08:17:34 +0000 [thread overview] Message-ID: <bug-115576-4-d328MFrll6@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 user202729 <user202729 at protonmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |user202729 at protonmail dot com --- Comment #4 from user202729 <user202729 at protonmail dot com> --- Doing a binary search reveals that the patch that causes the issue is https://gcc.gnu.org/pipermail/gcc-patches/2023-July/623766.html . Looking at the optimization process, the working is roughly the following: Before the change, the expand pass generates code that uses (set (subreg ...)). Then the split pass splits the register that is being used in subreg into two registers, then the combine pass do "constant propagation" and simplifies the code. After the change, the expand pass generates code that uses (set reg (ior (and reg 0xffff0000) value)). Thus the split pass cannot split the register (it does not know how to deal with "and", and the combine pass is similarly stuck.
next prev parent reply other threads:[~2024-06-25 8:17 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 ` [Bug c++/115576] [14/15 " rguenth at gcc dot gnu.org 2024-06-21 17:44 ` [Bug target/115576] " pinskia at gcc dot gnu.org 2024-06-25 8:17 ` user202729 at protonmail dot com [this message] 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-d328MFrll6@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).