public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112324] New: phiopt fail to recog if (b < 0) max = MAX(-b, max); else max = MAX (b, max) into max = MAX (ABS(b), max) Date: Wed, 01 Nov 2023 01:26:25 +0000 [thread overview] Message-ID: <bug-112324-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112324 Bug ID: 112324 Summary: phiopt fail to recog if (b < 0) max = MAX(-b, max); else max = MAX (b, max) into max = MAX (ABS(b), max) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: crazylht at gmail dot com Target Milestone: --- #define MAX(a, b) ((a) > (b) ? (a) : (b)) int foo (int n, int* a) { int max = 0; for (int i = 0; i != n; i++) { int tmp = a[i]; if (tmp < 0) max = MAX (-tmp, max); else max = MAX (tmp, max); } return max; } int foo1 (int n, int* a) { int max = 0; for (int i = 0; i != n; i++) { int tmp = a[i]; max = MAX ((tmp < 0 ? -tmp : tmp), max); } return max; } foo should be same as foo1, but gcc failed to recognize ABS_EXPR in foo. It's from pr110015(originally from source code in openjpeg).
next reply other threads:[~2023-11-01 1:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 1:26 crazylht at gmail dot com [this message] 2023-11-01 1:32 ` [Bug tree-optimization/112324] " pinskia at gcc dot gnu.org 2023-11-01 1:33 ` pinskia at gcc dot gnu.org 2023-11-06 17:27 ` pinskia at gcc dot gnu.org 2023-11-06 17:56 ` pinskia at gcc dot gnu.org 2023-11-06 20:23 ` pinskia at gcc dot gnu.org 2023-11-19 16:23 ` sjames at gcc dot gnu.org 2023-11-19 16:43 ` pinskia at gcc dot gnu.org 2023-11-19 17:13 ` 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-112324-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).