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/98709] gcc optimizes bitwise operations, but doesn't optimize logical ones
Date: Sun, 01 Aug 2021 18:17:44 +0000	[thread overview]
Message-ID: <bug-98709-4-6BXGIHGdCc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98709-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
         Depends on|                            |101706
   Last reconfirmed|                            |2021-08-01
          Component|middle-end                  |tree-optimization
             Status|UNCONFIRMED                 |NEW
           Severity|normal                      |enhancement

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.

I noticed the ~(a^b) issue the other day (not even knowing about this bug) and
filed PR 101706 for that :)


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101706
[Bug 101706] bool0^bool1^1 -> bool0 == bool1

  parent reply	other threads:[~2021-08-01 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17  1:31 [Bug middle-end/98709] New: " vanyacpp at gmail dot com
2021-01-17 17:34 ` [Bug middle-end/98709] " glisse at gcc dot gnu.org
2021-08-01 18:17 ` pinskia at gcc dot gnu.org [this message]
2022-08-10 11:46 ` [Bug tree-optimization/98709] " vanyacpp at gmail dot com
2022-10-22  2:13 ` 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-98709-4-6BXGIHGdCc@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).