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/108841] New: sometimes a < b && c < b is not optimized to MAX<a, c> < b Date: Sat, 18 Feb 2023 04:10:12 +0000 [thread overview] Message-ID: <bug-108841-4@http.gcc.gnu.org/bugzilla/> (raw) 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.
next reply other threads:[~2023-02-18 4:10 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-18 4:10 pinskia at gcc dot gnu.org [this message] 2023-02-20 8:20 ` [Bug tree-optimization/108841] " rguenth 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-108841-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: linkBe 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).