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/112096] `(a || b) ? a : b` should be simplified to a
Date: Thu, 26 Oct 2023 20:14:28 +0000	[thread overview]
Message-ID: <bug-112096-4-n6GdxtnJKE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112096-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-10-26
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |pinskia at gcc dot gnu.org

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
```
int t01(int x, int y)
{
  bool t = x == 5 && y == 5;
  if (t) return 5; return y;
} // y
```
Is able to be detected in phiopt2.  Just not the == 0/!=0 case.

Nor:
```
int t1(int x, int y)
{
  bool t = x != 5 || y != 5;
  if (t) return x; return 5;
} // x
```
I have to look at where phiopt is able to detect this and improve it for these
2 cases ...

  parent reply	other threads:[~2023-10-26 20:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  5:16 [Bug tree-optimization/112096] New: " pinskia at gcc dot gnu.org
2023-10-26  5:17 ` [Bug tree-optimization/112096] " pinskia at gcc dot gnu.org
2023-10-26 20:14 ` pinskia at gcc dot gnu.org [this message]
2023-10-26 20:22 ` pinskia at gcc dot gnu.org
2023-11-02 18:39 ` 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-112096-4-n6GdxtnJKE@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).