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 tree-optimization/108953] inefficient codegen for trivial equality Date: Tue, 28 Feb 2023 10:44:29 +0000 [thread overview] Message-ID: <bug-108953-4-s313zYLSQ1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108953-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108953 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-02-28 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- I think it only makes sense to combine the compares when the operand(s) are from memory which means the machinery we have in load/store merging becomes useful which means we eventually want to do this in this very pass (or in the bswap pass). The alternative would be ifcombine but then the order of the compares in the source could be arbitrary, so it doesn't really fit that one for the most optimal result. There's also a related vectorization bug in case the SLP vectorizer is the target to look at.
next prev parent reply other threads:[~2023-02-28 10:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 16:29 [Bug c++/108953] New: " barry.revzin at gmail dot com 2023-02-27 16:38 ` [Bug c++/108953] " pinskia at gcc dot gnu.org 2023-02-27 17:11 ` [Bug tree-optimization/108953] " jakub at gcc dot gnu.org 2023-02-28 10:44 ` rguenth at gcc dot gnu.org [this message] 2023-03-02 15:05 ` jakub at gcc dot gnu.org 2023-06-23 22:59 ` pinskia at gcc dot gnu.org 2023-07-13 18:15 ` [Bug c++/108953] " 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-108953-4-s313zYLSQ1@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).