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/107887] New: (bool0 > bool1) | bool1 is not optimized to bool0 | bool1
Date: Sun, 27 Nov 2022 18:59:44 +0000 [thread overview]
Message-ID: <bug-107887-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107887
Bug ID: 107887
Summary: (bool0 > bool1) | bool1 is not optimized to bool0 |
bool1
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
Take:
```
_Bool max(_Bool aa, _Bool bb)
{
bool t = aa > bb;
return t | bb;
}
```
This should be optimized to just `return aa | bb;`
I accidently found this while working on PR 101805 .
The original testcase which I found it:
```
int ii(_Bool aa, _Bool bb)
{
int c;
int a = aa;
int b = bb;
if (a > b)
c = a;
else
c = b;
if (c)
return 100;
return c;
}
```
next reply other threads:[~2022-11-27 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 18:59 pinskia at gcc dot gnu.org [this message]
2022-11-27 19:15 ` [Bug tree-optimization/107887] " pinskia at gcc dot gnu.org
2022-11-28 2:33 ` pinskia at gcc dot gnu.org
2022-11-28 2:51 ` pinskia at gcc dot gnu.org
2023-08-28 20:36 ` pinskia at gcc dot gnu.org
2023-08-28 21:30 ` pinskia at gcc dot gnu.org
2023-09-12 15:03 ` pinskia at gcc dot gnu.org
2023-09-24 4:57 ` 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-107887-4@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).