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/109702] [14 Regression] Wrong code with if and __builtin_bswap and others
Date: Tue, 02 May 2023 21:47:06 +0000	[thread overview]
Message-ID: <bug-109702-4-J1LCQe81Pq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109702-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:8702ab1456eee07d07ac1a8bc005c690cf6dbcf0

commit r14-413-g8702ab1456eee07d07ac1a8bc005c690cf6dbcf0
Author: Andrew Pinski <apinski@marvell.com>
Date:   Tue May 2 11:03:02 2023 -0700

    tree-optimization: [PR109702] MATCH: Fix a ? func(a) : N patterns

    I accidently messed up these patterns so the comparison
    against 0 and the arguments was not matching up when they
    need to be.

    I committed this as obvious after a bootstrap/test on x86_64-linux-gnu

            PR tree-optimization/109702

    gcc/ChangeLog:

            * match.pd: Fix "a != 0 ? FUNC(a) : CST" patterns
            for FUNC of POPCOUNT BSWAP FFS PARITY CLZ and CTZ.

    gcc/testsuite/ChangeLog:

            * gcc.dg/tree-ssa/phi-opt-25b.c: New test.

  parent reply	other threads:[~2023-05-02 21:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 17:33 [Bug tree-optimization/109702] New: " pinskia at gcc dot gnu.org
2023-05-02 17:34 ` [Bug tree-optimization/109702] " pinskia at gcc dot gnu.org
2023-05-02 21:47 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-02 22:05 ` 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-109702-4-J1LCQe81Pq@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).