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 tree-optimization/99918] [11/12/13/14 Regression] suboptimal code for bool bitfield tests
Date: Wed, 12 Jul 2023 22:05:04 +0000 [thread overview]
Message-ID: <bug-99918-4-xo3it4AdbQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99918-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99918
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu.org
--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #2)
> Bisection points to r225825 as the revision where GCC started to fail to
> fold the code in g().
the fold-const didn't check `types_match (type, TREE_TYPE (@0))` but rather
just did the equivalent to:
(simplify
(ne @0 integer_zerop@1)
(if (TREE_CODE (TREE_TYPE (@0)) == BOOLEAN_TYPE)
(non_lvalue (convert @0))))
While match now does not do the convert and checks the types_match check
instead.
prev parent reply other threads:[~2023-07-12 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 20:15 [Bug tree-optimization/99918] New: " msebor at gcc dot gnu.org
2021-04-05 20:22 ` [Bug tree-optimization/99918] " pinskia at gcc dot gnu.org
2021-04-05 20:23 ` [Bug tree-optimization/99918] [9/10/11 Regression] " msebor at gcc dot gnu.org
2021-04-05 20:27 ` msebor at gcc dot gnu.org
2021-04-05 20:40 ` msebor at gcc dot gnu.org
2021-04-06 8:39 ` rguenth at gcc dot gnu.org
2021-04-08 14:22 ` rguenth at gcc dot gnu.org
2021-06-01 8:20 ` [Bug tree-optimization/99918] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27 9:44 ` [Bug tree-optimization/99918] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:44 ` jakub at gcc dot gnu.org
2022-07-01 12:49 ` fkorta at gmail dot com
2023-07-07 10:39 ` [Bug tree-optimization/99918] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-12 22:05 ` pinskia at gcc dot gnu.org [this message]
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-99918-4-xo3it4AdbQ@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).