public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100958] two_value_replacement should move to match.pd
Date: Fri, 28 Apr 2023 14:27:42 +0000	[thread overview]
Message-ID: <bug-100958-4-Vz6ZY3jrG1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100958-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100958

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:1dd154f6407658d46faa4d21bfec04fc2551506a

commit r14-338-g1dd154f6407658d46faa4d21bfec04fc2551506a
Author: Andrew Pinski <apinski@marvell.com>
Date:   Tue Apr 25 19:46:40 2023 -0700

    PHIOPT: Move two_value_replacement to match.pd

    This patch converts two_value_replacement function
    into a match.pd pattern.
    It is a direct translation with only one minor change,
    does not check for the {0,+-1} case as that is handled
    before in match.pd so there is no reason to do the extra
    check for it.

    OK? Bootstrapped and tested on x86_64-linux-gnu with
    no regressions.

    gcc/ChangeLog:

            PR tree-optimization/100958
            * tree-ssa-phiopt.cc (two_value_replacement): Remove.
            (pass_phiopt::execute): Don't call two_value_replacement.
            * match.pd (a !=/== CST1 ? CST2 : CST3): Add pattern to
            handle what two_value_replacement did.

  parent reply	other threads:[~2023-04-28 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  6:42 [Bug tree-optimization/100958] New: " pinskia at gcc dot gnu.org
2021-06-08  6:42 ` [Bug tree-optimization/100958] " pinskia at gcc dot gnu.org
2023-04-09 17:21 ` pinskia at gcc dot gnu.org
2023-04-26  3:01 ` pinskia at gcc dot gnu.org
2023-04-28 14:27 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-28 14:50 ` 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-100958-4-Vz6ZY3jrG1@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).