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/111282] `a & (b ^ ~a)` (or `a & ~(a ^ b)`) not optimized to `a & b` in gimple
Date: Mon, 04 Sep 2023 07:26:07 +0000	[thread overview]
Message-ID: <bug-111282-4-9InBzdYZs9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111282-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note `|` case already handled by r8-4395:
/* a | ~(a ^ b)  -->  a | ~b  */
(simplify
 (bit_ior:c @0 (bit_not:s (bit_xor:c @0 @1)))
 (bit_ior @0 (bit_not @1)))

  parent reply	other threads:[~2023-09-04  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  6:03 [Bug tree-optimization/111282] New: " pinskia at gcc dot gnu.org
2023-09-04  6:04 ` [Bug tree-optimization/111282] " pinskia at gcc dot gnu.org
2023-09-04  6:09 ` pinskia at gcc dot gnu.org
2023-09-04  7:26 ` pinskia at gcc dot gnu.org [this message]
2023-10-03  3:12 ` pinskia at gcc dot gnu.org
2023-10-10 20:03 ` pinskia at gcc dot gnu.org
2023-10-11  0:48 ` pinskia at gcc dot gnu.org
2023-10-11 16:46 ` cvs-commit at gcc dot gnu.org
2023-10-11 16:47 ` 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-111282-4-9InBzdYZs9@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).