public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100864] (a&!b) | b is not opimized to a | b for comparisons
Date: Wed, 02 Jun 2021 08:09:22 +0000	[thread overview]
Message-ID: <bug-100864-4-Y7KvshSJBp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100864-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
You can possibly merge it with the

(for bitop (bit_and bit_ior)
     rbitop (bit_ior bit_and)
  /* (x | y) & x -> x */
  /* (x & y) | x -> x */
 (simplify
  (bitop:c (rbitop:c @0 @1) @0)
  @0)
 /* (~x | y) & x -> x & y */
 /* (~x & y) | x -> x | y */
 (simplify
  (bitop:c (rbitop:c (bit_not @0) @1) @0)
  (bitop @0 @1)))

by using sth like logical_inverted_value (you want bit_inverted_value),

Also you don't need

 (for cmp (tcc_comparison)
  (for icmp (tcc_comparison)

but just

  (for cmp (tcc_comparison)
       icmp (inverted_tcc_comparison)
       ncmp (inverted_tcc_comparison_with_nans))
    ...
   (if (ic == icmp || ic == ncmp)
...

right?

  parent reply	other threads:[~2021-06-02  8:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 23:48 [Bug tree-optimization/100864] New: (a&!b) | b is not opimized to a | b for conditionals pinskia at gcc dot gnu.org
2021-06-02  1:33 ` [Bug tree-optimization/100864] (a&!b) | b is not opimized to a | b for comparisons pinskia at gcc dot gnu.org
2021-06-02  2:05 ` pinskia at gcc dot gnu.org
2021-06-02  8:09 ` rguenth at gcc dot gnu.org [this message]
2021-06-05  1:21 ` pinskia at gcc dot gnu.org
2021-06-14 22:04 ` pinskia at gcc dot gnu.org
2023-05-24  0:09 ` pinskia at gcc dot gnu.org
2023-07-22 23:28 ` pinskia at gcc dot gnu.org
2023-07-29 19:10 ` pinskia at gcc dot gnu.org
2023-07-31 17:12 ` cvs-commit at gcc dot gnu.org
2023-07-31 17:14 ` 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-100864-4-Y7KvshSJBp@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).