public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114151] [14 Regression] weird and inefficient codegen and addressing modes since r14-9193 Date: Wed, 06 Mar 2024 07:31:58 +0000 [thread overview] Message-ID: <bug-114151-4-3o8v6zbj2f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114151-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114151 --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Richard Biener from comment #10) > (In reply to Andrew Macleod from comment #9) > > Created attachment 57620 [details] > > proposed patch > > > > Does this solve your problem if there is an active ranger? it bootstraps > > with no regressions > > I'll check what it does. So it does seem to help, not on the testcases ultimate outcome, but for the important bits of the analysis. With adding an active ranger around IVOPTs with diff --git a/gcc/tree-ssa-loop-ivopts.cc b/gcc/tree-ssa-loop-ivopts.cc index 7cae5bdefea..626fc5bf5d7 100644 --- a/gcc/tree-ssa-loop-ivopts.cc +++ b/gcc/tree-ssa-loop-ivopts.cc @@ -132,6 +132,7 @@ along with GCC; see the file COPYING3. If not see #include "tree-vectorizer.h" #include "dbgcnt.h" #include "cfganal.h" +#include "gimple-range.h" /* For lang_hooks.types.type_for_mode. */ #include "langhooks.h" @@ -8280,6 +8281,8 @@ tree_ssa_iv_optimize (void) tree_ssa_iv_optimize_init (&data); mark_ssa_maybe_undefs (); + enable_ranger (cfun); + /* Optimize the loops starting with the innermost ones. */ for (auto loop : loops_list (cfun, LI_FROM_INNERMOST)) { @@ -8292,6 +8295,8 @@ tree_ssa_iv_optimize (void) tree_ssa_iv_optimize_loop (&data, loop, toremove); } + disable_ranger (cfun); + /* Remove eliminated IV defs. */ release_defs_bitset (toremove); I then see the following difference with a ranger-debug dump during IVOPTs: 11 range_of_expr(_12) - TRUE : (11) range_of_expr (_12) [irange] int VARYING + TRUE : (11) range_of_expr (_12) [irange] int [0, +INF] ... Base: (long unsigned int) (int) ((unsigned int) _12 + 1) * 2 Step: 2 Biv: N - Overflowness wrto loop niter: Overflow + Overflowness wrto loop niter: No-overflow ... -74 range_of_expr(_103) - TRUE : (74) range_of_expr (_103) [irange] int VARYING +64 range_of_expr(_103) + TRUE : (64) range_of_expr (_103) [irange] int [-INF, 0] Analyzing # of iterations of loop 1 exit condition [1, + , 1](no_overflow) <= _103 - bounds on difference of bases: -2147483649 ... 2147483646 + bounds on difference of bases: -2147483649 ... -1 result: zero if _103 < 0 - # of iterations (unsigned int) _103, bounded by 2147483647 + # of iterations (unsigned int) _103, bounded by 0 So the important part is that it got the fact that _12 is positive. As analyzed in earlier comments I think that's all we can do, we don't know anything about the other variable involved and thus can't avoid the unsigned punning during SCEV analysis. I think it's a good change, let's keep it queued for stage1 at this point unless we really know a case it helps to avoid a regression with r14-9193-ga0b1798042d033 For testing, what's the "easiest" pass/thing to do to recompute global ranges now? In the past I'd schedule EVRP but is there now a ranger API to do this? Just to see if full global range compute before IVOPTs would help.
next prev parent reply other threads:[~2024-03-06 7:31 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 13:57 [Bug tree-optimization/114151] New: [14 Regression] weird and inefficient codegen and addressing modes since g:a0b1798042d033fd2cc2c806afbb77875dd2909b tnfchris at gcc dot gnu.org 2024-02-28 14:33 ` [Bug tree-optimization/114151] " rguenth at gcc dot gnu.org 2024-02-28 14:36 ` rguenth at gcc dot gnu.org 2024-02-28 16:51 ` tnfchris at gcc dot gnu.org 2024-02-29 7:19 ` rguenther at suse dot de 2024-02-29 18:15 ` amacleod at redhat dot com 2024-03-01 9:37 ` rguenth at gcc dot gnu.org 2024-03-01 15:02 ` [Bug tree-optimization/114151] [14 Regression] weird and inefficient codegen and addressing modes since r14-9193 amacleod at redhat dot com 2024-03-04 7:47 ` rguenth at gcc dot gnu.org 2024-03-06 3:37 ` amacleod at redhat dot com 2024-03-06 7:14 ` rguenth at gcc dot gnu.org 2024-03-06 7:31 ` rguenth at gcc dot gnu.org [this message] 2024-03-06 14:57 ` amacleod at redhat dot com 2024-03-06 20:05 ` amacleod at redhat dot com 2024-03-07 8:04 ` rguenth at gcc dot gnu.org 2024-03-07 15:53 ` amacleod at redhat dot com 2024-03-07 20:37 ` law at gcc dot gnu.org 2024-03-08 10:13 ` rguenth at gcc dot gnu.org 2024-03-08 10:22 ` tnfchris at gcc dot gnu.org 2024-03-08 14:10 ` rguenth at gcc dot gnu.org 2024-03-12 9:59 ` rguenth at gcc dot gnu.org 2024-03-12 10:00 ` rguenth at gcc dot gnu.org 2024-03-12 20:41 ` amacleod at redhat dot com 2024-03-13 7:38 ` rguenth at gcc dot gnu.org 2024-03-13 17:37 ` amacleod at redhat dot com 2024-03-19 12:12 ` cvs-commit at gcc dot gnu.org 2024-03-19 12:16 ` 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-114151-4-3o8v6zbj2f@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).