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/95923] Failure to optimize bool checks into and
Date: Sun, 16 Jul 2023 00:02:33 +0000	[thread overview]
Message-ID: <bug-95923-4-VMX7Art6H7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95923-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So there are some patterns for non boolean as for boolean values ~(a^b) is
converted to a==b so we need to support the == case for these:
```
/* (a | b) & ~(a ^ b)  -->  a & b  */
(simplify
 (bit_and:c (bit_ior @0 @1) (bit_not (bit_xor:c @0 @1)))
 (bit_and @0 @1))

/* a | ~(a ^ b)  -->  a | ~b  */
(simplify
 (bit_ior:c @0 (bit_not:s (bit_xor:c @0 @1)))
 (bit_ior @0 (bit_not @1)))

/* (a & b) | ~(a ^ b)  -->  ~(a ^ b)  */
(simplify
 (bit_ior:c (bit_and:c @0 @1) (bit_not@2 (bit_xor @0 @1)))
 @2)
```

So mine.

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27  0:49 [Bug tree-optimization/95923] New: " gabravier at gmail dot com
2020-06-27 12:54 ` [Bug tree-optimization/95923] " glisse at gcc dot gnu.org
2021-04-26  1:03 ` pinskia at gcc dot gnu.org
2021-08-07  7:41 ` pinskia at gcc dot gnu.org
2023-06-11 19:27 ` pinskia at gcc dot gnu.org
2023-07-16  0:02 ` pinskia at gcc dot gnu.org [this message]
2023-07-16  0:17 ` pinskia at gcc dot gnu.org
2023-07-16 22:57 ` pinskia at gcc dot gnu.org
2023-07-16 22:57 ` pinskia at gcc dot gnu.org
2023-07-17  2:44 ` pinskia at gcc dot gnu.org
2023-07-17  6:43 ` cvs-commit at gcc dot gnu.org
2023-07-17  6:45 ` 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-95923-4-VMX7Art6H7@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).