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/106677] Abstraction overhead with std::views::join
Date: Fri, 25 Aug 2023 16:36:48 +0000	[thread overview]
Message-ID: <bug-106677-4-I186qaJCqF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106677-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:6df8dcec7196e42ca2eed69e1ae455bae8d0fe93

commit r14-3485-g6df8dcec7196e42ca2eed69e1ae455bae8d0fe93
Author: Andrew Pinski <apinski@marvell.com>
Date:   Sat Aug 19 17:56:46 2023 -0700

    MATCH: `a | C -> C` when we know that `a & ~C == 0`

    Even though this is handled by other code inside both VRP and CCP,
    sometimes we want to optimize this outside of VRP and CCP.
    An example is given in PR 106677 where phiopt will happen
    after VRP (which removes a cast for a comparison) and then
    phiopt will optimize the phi to be `a | 1` which can then
    be optimized to `1` due to this patch.

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

    Note Similar code already exists in simplify_rtx for the RTL level;
    it was moved from combine to simplify_rtx in r0-72539-gbd1ef757767f6d.
    gcc/ChangeLog:

            * match.pd (`a | C -> C`): New pattern.

  parent reply	other threads:[~2023-08-25 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-106677-4@http.gcc.gnu.org/bugzilla/>
2023-05-06 21:03 ` pinskia at gcc dot gnu.org
2023-08-19 22:03 ` pinskia at gcc dot gnu.org
2023-08-24 23:39 ` pinskia at gcc dot gnu.org
2023-08-25 16:36 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-25 18:34 ` cvs-commit 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-106677-4-I186qaJCqF@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).