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: Tue, 08 Jun 2021 23:09:32 +0000	[thread overview]
Message-ID: <bug-25290-4-YbyGwySv5T@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 #22 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Without load/store handling, here are the following optimizations that either
can move to match.pd already or need some extra work to do it:

* value_replacement: need to handle !single_non_singleton_phi_for_edges case
and more than one feeder statement (2 max according to the current definition)
* cond_removal_in_popcount_clz_ctz_pattern: need 2 feeder statements and
builtin call handling for feeder statements


* two_value_replacement: recored as PR 100958, it can move already
* abs_replacement: needs PROP_gimple_lswitch so we don't change if statements
early enough
** I think majority of the abs handling is already in match.pd.
* minmax_replacement: has some handling of comparisions which might not be in
the match.pd patterns already.  needs PROP_gimple_lswitch also.
** The handling of:
         if (a <= u)
           b = MAX (a, d);
         x = PHI <b, u>
   needs to moved too.


For the ones which cannot move
* factor_out_conditional_conversion: will never move, though it needs
improvement and moved already (PR 56223 and PR 13563)
* spaceship_replacement: cannot move to match.pd depends on use afterwards
which is not hard to deal with in a match pattern.

  parent reply	other threads:[~2021-06-08 23:09 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 [this message]
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
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-YbyGwySv5T@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).