public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110992] [13/14 Regression] missed VRP optimization due to transformation of `a & -zero_one_valued_p` into `a * zero_one_valued_p`
Date: Sat, 09 Mar 2024 08:55:06 +0000 [thread overview]
Message-ID: <bug-110992-4-jLWwXpaxtx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110992-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110992
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=111126
--- Comment #14 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #13)
> So like the other bug involving multiplies against objects with a known
> range [0,1], we should very seriously consider turning the multiply into a
> conditional move. ie x * b where b is known to have the range [0,1] we can
> turn that into
>
> dest = b ? x : 0
>
> Some processors that don't have generalized conditional moves do have
> conditional zero instructions. ie, zicond on RISC-V.
It's PR111126.
next prev parent reply other threads:[~2024-03-09 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 13:24 [Bug tree-optimization/110992] New: [14 Regression] Dead Code Elimination Regression at -O3 since r14-1654-g7ceed7e3e29 scherrer.sv at gmail dot com
2023-08-11 17:38 ` [Bug tree-optimization/110992] " pinskia at gcc dot gnu.org
2023-08-26 0:30 ` pinskia at gcc dot gnu.org
2023-09-14 21:11 ` pinskia at gcc dot gnu.org
2023-09-14 21:22 ` pinskia at gcc dot gnu.org
2023-09-15 3:19 ` [Bug tree-optimization/110992] [13/14 Regression] missed VRP optimization due to transformation of `a & -zero_one_valued_p` into `a * zero_one_valued_p` pinskia at gcc dot gnu.org
2023-09-15 3:54 ` pinskia at gcc dot gnu.org
2023-09-15 4:13 ` pinskia at gcc dot gnu.org
2023-09-15 4:33 ` pinskia at gcc dot gnu.org
2023-09-15 16:28 ` pinskia at gcc dot gnu.org
2023-09-15 22:45 ` pinskia at gcc dot gnu.org
2023-09-16 16:33 ` pinskia at gcc dot gnu.org
2023-09-18 23:51 ` pinskia at gcc dot gnu.org
2024-03-07 23:24 ` law at gcc dot gnu.org
2024-03-09 6:40 ` law at gcc dot gnu.org
2024-03-09 8:55 ` xry111 at gcc dot gnu.org [this message]
2024-05-21 9:16 ` [Bug tree-optimization/110992] [13/14/15 " jakub 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-110992-4-jLWwXpaxtx@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).