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/110199] New: [12/13/14 Regression] Missing VRP transformation with MIN_EXPR and known relation Date: Fri, 09 Jun 2023 22:28:13 +0000 [thread overview] Message-ID: <bug-110199-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110199 Bug ID: 110199 Summary: [12/13/14 Regression] Missing VRP transformation with MIN_EXPR and known relation Product: gcc Version: 14.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: ``` int test(int a, int b) { if (a <= b) return a < b ? a : b; return 0; } ``` This used to be optimized in GCC 11 and before via EVRP: pushing new range for b_3(D): int [a_2(D), +INF] EQUIVALENCES: { b_3(D) } (1 elements) evrp visiting stmt _5 = MIN_EXPR <a_2(D), b_3(D)>; extract_range_from_stmt visiting: _5 = MIN_EXPR <a_2(D), b_3(D)>; Intersecting int VARYING and int VARYING to int VARYING Folding statement: _5 = MIN_EXPR <a_2(D), b_3(D)>; Folded into: _5 = a_2(D); But in GCC 12 and above it is missed: Folding statement: _5 = MIN_EXPR <a_2(D), b_3(D)>; folding with relation a_2(D) <= b_3(D) Not folded
next reply other threads:[~2023-06-09 22:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-09 22:28 pinskia at gcc dot gnu.org [this message] 2023-06-09 22:28 ` [Bug tree-optimization/110199] " pinskia at gcc dot gnu.org 2023-06-09 22:29 ` pinskia at gcc dot gnu.org 2023-06-12 8:11 ` rguenth at gcc dot gnu.org 2023-08-11 23:57 ` pinskia at gcc dot gnu.org 2023-12-12 21:59 ` amacleod at redhat dot com 2024-03-06 16:13 ` jakub at gcc dot gnu.org 2024-03-06 16:47 ` amacleod at redhat dot com 2024-03-07 13:34 ` law at gcc dot gnu.org 2024-03-10 18:05 ` cvs-commit 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-110199-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).