public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114277] [11/12/13/14 Regression] Missed optimization: x*(x||b) => x
Date: Sat, 09 Mar 2024 03:56:52 +0000 [thread overview]
Message-ID: <bug-114277-4-dFCymKaRTY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114277-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114277
Jeffrey A. Law <law at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at gcc dot gnu.org,
| |rzinsly at ventanamicro dot com
--- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> ---
The other approach we could take (and which I think may have certain
advantages) would be to first realize this is a multiplication by a boolean
(0/1) value. That's just a conditional move. If we then rewrote as a
conditional move there's a reasonable chance we'd be able to further simplify.
The biggest problem with this approach is if we're aggressively transforming
into conditional moves in gimple, the expanders will need improvement,
particularly on targets that don't have conditional moves.
Raphael has a TODO in this space. He may have further thoughts.
next prev parent reply other threads:[~2024-03-09 3:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 5:31 [Bug tree-optimization/114277] New: " 652023330028 at smail dot nju.edu.cn
2024-03-08 6:10 ` [Bug tree-optimization/114277] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-03-08 10:24 ` rguenth at gcc dot gnu.org
2024-03-09 3:56 ` law at gcc dot gnu.org [this message]
2024-03-11 17:11 ` rzinsly at ventanamicro dot com
2024-03-11 17:33 ` pinskia at gcc dot gnu.org
2024-03-11 23:36 ` pinskia at gcc dot gnu.org
2024-03-12 0:45 ` 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-114277-4-dFCymKaRTY@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).