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/111364] New: `MAX_EXPR<a, b> <= a` is not optimized to `a >= b` Date: Sun, 10 Sep 2023 21:11:08 +0000 [thread overview] Message-ID: <bug-111364-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111364 Bug ID: 111364 Summary: `MAX_EXPR<a, b> <= a` is not optimized to `a >= b` Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: tree-optimization Assignee: pinskia at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- I Noticed this while looking into PR 111346: ``` _Bool test2(int a, int b) { int t = a; if (t < b) t = b; return t <= a; } ``` Should be optimized to just: ``` return a >= b; ``` There is a pattern for constants: /* MIN (X, C1) < C2 -> X < C2 || C1 < C2 */ But we could do the same when we know C1 == C2 and not constant (for !HONOR_NANS & !HONOR_SIGNED_ZEROS).
next reply other threads:[~2023-09-10 21:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-10 21:11 pinskia at gcc dot gnu.org [this message] 2023-09-10 21:11 ` [Bug tree-optimization/111364] " pinskia at gcc dot gnu.org 2023-09-12 0:14 ` pinskia at gcc dot gnu.org 2023-09-12 0:36 ` pinskia at gcc dot gnu.org 2023-09-12 0:36 ` pinskia at gcc dot gnu.org 2023-09-12 5:36 ` pinskia at gcc dot gnu.org 2023-09-12 15:40 ` pinskia at gcc dot gnu.org 2023-09-13 12:07 ` cvs-commit at gcc dot gnu.org 2023-09-13 12:08 ` 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-111364-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).