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 middle-end/110726] [14 Regression] wrong code on llvm-16 around 'a |= a == 0'
Date: Wed, 19 Jul 2023 16:16:29 +0000	[thread overview]
Message-ID: <bug-110726-4-XB5UCeYfFy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110726-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 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:bf20b770d9aabb15faf2644b5e3106249cb175f3

commit r14-2648-gbf20b770d9aabb15faf2644b5e3106249cb175f3
Author: Andrew Pinski <apinski@marvell.com>
Date:   Tue Jul 18 21:11:46 2023 +0000

    Fix PR110726: a | (a == b) can sometimes produce wrong code

    So I had missed/forgot that EQ_EXPR could have an non boolean
    type for generic when I implemented r14-2556-g0407ae8a7732d9.
    This patch adds check for one bit precision intergal type
    which fixes the problem.

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

            PR tree-optimization/110726

    gcc/ChangeLog:

            * match.pd ((a|b)&(a==b),a|(a==b),(a&b)|(a==b)):
            Add checks to make sure the type was one bit precision
            intergal type.

    gcc/testsuite/ChangeLog:

            * gcc.c-torture/execute/bitops-1.c: New test.

  parent reply	other threads:[~2023-07-19 16:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 19:09 [Bug middle-end/110726] New: " slyfox at gcc dot gnu.org
2023-07-18 19:29 ` [Bug middle-end/110726] " pinskia at gcc dot gnu.org
2023-07-18 19:29 ` pinskia at gcc dot gnu.org
2023-07-18 19:32 ` pinskia at gcc dot gnu.org
2023-07-18 19:36 ` pinskia at gcc dot gnu.org
2023-07-18 19:36 ` pinskia at gcc dot gnu.org
2023-07-18 19:39 ` pinskia at gcc dot gnu.org
2023-07-18 20:04 ` pinskia at gcc dot gnu.org
2023-07-18 20:31 ` pinskia at gcc dot gnu.org
2023-07-18 21:37 ` slyfox at gcc dot gnu.org
2023-07-18 21:42 ` pinskia at gcc dot gnu.org
2023-07-19  2:02 ` pinskia at gcc dot gnu.org
2023-07-19  6:13 ` slyfox at gcc dot gnu.org
2023-07-19 16:16 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-19 16:17 ` 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-110726-4-XB5UCeYfFy@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).