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/104376] Failure to optimize clz equivalent to clz
Date: Wed, 09 Feb 2022 07:40:18 +0000 [thread overview]
Message-ID: <bug-104376-4-43nSVlBZXn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104376-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104376
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=101822,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=99997,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=71016
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> cond_removal_in_builtin_zero_pattern should have optimized the above but
> does not for some reason.
> Let me take a look.
So one problem is we have:
<bb 2> [local count: 1073741824]:
if (x_3(D) == 0)
goto <bb 4>; [21.72%]
else
goto <bb 3>; [78.28%]
<bb 3> [local count: 840525097]:
_1 = __builtin_clz (x_3(D));
_4 = (uint32_t) _1;
<bb 4> [local count: 1073741824]:
# _2 = PHI <32(2), _4(3)>
Which we don't handle in cond_removal_in_builtin_zero_pattern, this similar to
PR 99997 and PR 101822, that is the code which added to fix PR 71016 is getting
in the way.
next prev parent reply other threads:[~2022-02-09 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 1:10 [Bug tree-optimization/104376] New: " gabravier at gmail dot com
2022-02-04 4:26 ` [Bug tree-optimization/104376] " pinskia at gcc dot gnu.org
2022-02-04 4:27 ` pinskia at gcc dot gnu.org
2022-02-04 7:01 ` pinskia at gcc dot gnu.org
2022-02-09 6:10 ` pinskia at gcc dot gnu.org
2022-02-09 7:40 ` pinskia at gcc dot gnu.org [this message]
2023-05-06 21:23 ` pinskia at gcc dot gnu.org
2023-10-15 18:58 ` pinskia at gcc dot gnu.org
2023-10-15 19:21 ` pinskia at gcc dot gnu.org
2023-10-24 11:17 ` cvs-commit at gcc dot gnu.org
2023-10-24 11:20 ` 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-104376-4-43nSVlBZXn@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).