public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91213] Missed optimization: (sub X Y) -> (xor X Y) when Y <= X and isPowerOf2(X + 1)
Date: Mon, 29 Aug 2022 15:25:44 +0000 [thread overview]
Message-ID: <bug-91213-4-1aoxTqUjFe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91213-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91213
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to rdapp from comment #6)
> What's the mechanism to get range information at RTL level? The only related
> thing I saw in (e.g.) simplify-rtx.cc is nonzero_bits and this does not seem
> to be propagated from gimple.
You can get it at expand time, is that enough? Which I think the patch I had.
As far as nonzero_bits there is a project being working by Segher but I don't
know the status of it.
next prev parent reply other threads:[~2022-08-29 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91213-4@http.gcc.gnu.org/bugzilla/>
2021-08-03 23:14 ` [Bug tree-optimization/91213] " pinskia at gcc dot gnu.org
2021-08-03 23:15 ` pinskia at gcc dot gnu.org
2022-08-24 15:02 ` [Bug middle-end/91213] " pinskia at gcc dot gnu.org
2022-08-24 15:03 ` pinskia at gcc dot gnu.org
2022-08-29 7:42 ` rdapp at gcc dot gnu.org
2022-08-29 15:25 ` pinskia at gcc dot gnu.org [this message]
2022-08-31 9:27 ` rdapp at gcc dot gnu.org
2022-08-31 9:36 ` rdapp 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-91213-4-1aoxTqUjFe@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).