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/25290] PHI-OPT could be rewritten so that is uses match
Date: Mon, 10 Apr 2023 07:31:30 +0000 [thread overview]
Message-ID: <bug-25290-4-kKNASDjGGM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-25290-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25290
--- Comment #29 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #28)
> Created attachment 54821 [details]
> New set of patches including some other improvements
Note this series does not bootstrap, the last patch found that I had a latent
bug in the patch that started to handle diamond shaped PHIs.
For:
if (_16 == 34)
goto <bb 10>; [INV]
else
goto <bb 12>; [INV]
<bb 10> :
...
_27 = csets__identifier_char[_26];
if (_27 != 0)
goto <bb 11>; [INV]
else
goto <bb 12>; [INV]
<bb 11> :
// predicted unlikely by early return (on trees) predictor.
goto <bb 13>; [INV]
<bb 12> :
// predicted unlikely by early return (on trees) predictor.
<bb 13> :
# _28 = PHI <1(7), 0(12), 1(4), 1(11)>
I would transform it to use _27 even from bb 12 which is wrong.
I had missed that minmax_replacement did:
if (!single_pred_p (middle_bb)
|| !single_pred_p (alt_middle_bb)
|| !single_succ_p (middle_bb)
|| !single_succ_p (alt_middle_bb))
return false;
I will add that check tomorrow.
next prev parent reply other threads:[~2023-04-10 7:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25290-4@http.gcc.gnu.org/bugzilla/>
2012-01-21 22:04 ` [Bug tree-optimization/25290] PHI-OPT could be rewritten so that is uses fold pinskia at gcc dot gnu.org
2012-02-24 0:04 ` pinskia at gcc dot gnu.org
2013-05-19 9:43 ` glisse at gcc dot gnu.org
2014-11-05 15:43 ` pinskia at gcc dot gnu.org
2014-11-06 4:04 ` pinskia at gcc dot gnu.org
2021-05-15 4:19 ` [Bug tree-optimization/25290] PHI-OPT could be rewritten so that is uses match pinskia at gcc dot gnu.org
2021-05-16 0:50 ` pinskia at gcc dot gnu.org
2021-06-01 18:51 ` cvs-commit at gcc dot gnu.org
2021-06-01 18:53 ` pinskia at gcc dot gnu.org
2021-06-05 1:41 ` pinskia at gcc dot gnu.org
2021-06-08 22:13 ` cvs-commit at gcc dot gnu.org
2021-06-08 22:47 ` pinskia at gcc dot gnu.org
2021-06-08 23:09 ` pinskia at gcc dot gnu.org
2021-06-09 7:14 ` rguenther at suse dot de
2021-06-23 22:25 ` pinskia at gcc dot gnu.org
2021-07-06 7:43 ` pinskia at gcc dot gnu.org
2022-11-18 21:46 ` pinskia at gcc dot gnu.org
2023-04-05 19:30 ` pinskia at gcc dot gnu.org
2023-04-10 5:50 ` pinskia at gcc dot gnu.org
2023-04-10 7:31 ` pinskia at gcc dot gnu.org [this message]
2023-04-27 2:54 ` pinskia at gcc dot gnu.org
2023-05-05 6:24 ` pinskia at gcc dot gnu.org
2023-10-21 21:18 ` pinskia at gcc dot gnu.org
2024-04-19 1:23 ` pinskia at gcc dot gnu.org
2024-05-02 21:54 ` 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-25290-4-kKNASDjGGM@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).