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 target/94892] (x >> 31) + 1 not getting narrowed to compare
Date: Thu, 30 Apr 2020 18:34:40 +0000 [thread overview]
Message-ID: <bug-94892-4-maWbq2B5MY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94892-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94892
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|tree-optimization |target
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
GCC's code gen is actually better than LLVM's here I think.
next prev parent reply other threads:[~2020-04-30 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 17:25 [Bug tree-optimization/94892] New: " gabravier at gmail dot com
2020-04-30 18:34 ` pinskia at gcc dot gnu.org [this message]
2020-04-30 19:32 ` [Bug target/94892] " gabravier at gmail dot com
2020-05-01 19:28 ` harald at gigawatt dot nl
2020-08-10 0:19 ` gabravier at gmail dot com
2021-12-15 0:23 ` [Bug tree-optimization/94892] " pinskia at gcc dot gnu.org
2021-12-15 0:31 ` pinskia at gcc dot gnu.org
2023-05-28 23:15 ` 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-94892-4-maWbq2B5MY@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).