public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/108841] New: sometimes a < b && c < b is not optimized to MAX<a, c> < b
@ 2023-02-18 4:10 pinskia at gcc dot gnu.org
2023-02-20 8:20 ` [Bug tree-optimization/108841] " rguenth at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-02-18 4:10 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108841
Bug ID: 108841
Summary: sometimes a < b && c < b is not optimized to MAX<a, c>
< b
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
Take:
```
int f1(int a0, int a1, int b, int c0, int c1)
{
int a = a0 < a1 ? a1 : a0;
if (a < b) {
int c = c0 < c1 ? c1 : c0;
if (c < b)
return 0;
}
return 1;
}
int f2(int a0, int a1, int b, int c0, int c1)
{
int a = a0 < a1 ? a1 : a0;
int c = c0 < c1 ? c1 : c0;
if (a < b) {
if (c < b)
return 0;
}
return 1;
}
```
These 2 functions should produce the same code, the only difference is the
calculation of c is not condtional.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-02-20 8:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-18 4:10 [Bug tree-optimization/108841] New: sometimes a < b && c < b is not optimized to MAX<a, c> < b pinskia at gcc dot gnu.org
2023-02-20 8:20 ` [Bug tree-optimization/108841] " rguenth at gcc dot gnu.org
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).