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/103536] Suboptimal codegen for && and || combination.
Date: Wed, 23 Aug 2023 03:29:48 +0000	[thread overview]
Message-ID: <bug-103536-4-daJYaNLkgA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103536-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |pinskia at gcc dot gnu.org

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
After r14-1597-g64d90d06d2db , we are just missing:
```
int
src_int (int a, int b)
{
    return (a | b) & (a & b);
}
```
into:
```
int
src_int_ (int a, int b)
{
    return (a & b);
}
```
Which is detected at the RTL level though.

This is 

So mine:
```
(for bitop (bit_and bit_ior)
     rbitop (bit_ior bit_and)
  /* (x | y) & (x & z) -> (x & z) */
  /* (x & y) | (x | z) -> (x | z) */
 (simplify
  (bitop:c (rbitop:c @0 @1) (bitop:c@3 @0 @2))
  @3)
```

  parent reply	other threads:[~2023-08-23  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  1:37 [Bug tree-optimization/103536] New: " navidr at gcc dot gnu.org
2021-12-06  8:18 ` [Bug tree-optimization/103536] " rguenth at gcc dot gnu.org
2022-03-16  8:37 ` coenraad at wish dot org.za
2023-08-23  3:29 ` pinskia at gcc dot gnu.org [this message]
2023-09-03  4:04 ` pinskia at gcc dot gnu.org
2023-09-03 20:54 ` pinskia at gcc dot gnu.org
2023-09-05 21:16 ` cvs-commit at gcc dot gnu.org
2023-09-05 21: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-103536-4-daJYaNLkgA@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).