public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <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: Thu, 07 Mar 2024 15:53:41 +0000 [thread overview] Message-ID: <bug-114151-4-7FiFkX6TpS@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 #15 from Andrew Macleod <amacleod at redhat dot com> --- (In reply to Richard Biener from comment #14) > (In reply to Andrew Macleod from comment #13) > > > > We would have tripped over this earlier if SCEV or one of those other places > > using range_of_expr without context had instead invoked range_of_stmt. That > > would have been perfectly reasonable, and would have resulting in these same > > issues. We never tripped over it because range_of_stmt is not used much > > outside of ranger. That is the primary reason I wanted to track this down. > > There were alternative paths to the same end result that would have > > triggered these issues. > > It sounds like this part is a bugfix? Technically yes. When I commit it to trunk, I would split this into 3 patches. 1 - The change to get_global_range to not process PHIS. This is only a bug that shows up if range_of_stmt is called from within SCEV. 2 - Make cache propagation re-entrant This is also only currently needed if SCEV invokes range_of_stmt 3 - call range_of_stmt from range_of_expr when context-less. This patch causes SCEV to call range_of_stmt indirectly through range_of_expr. I don't think the buglet would show up in the current release simply because SCEV never calls ranger with a context, and thus range_of_stmt never gets invoked by it. It might be worthwhile to put the patchset (or at least the first 2?) in the first point release after they've been committed to trunk in case something else wants to be backported which trips over it.
next prev parent reply other threads:[~2024-03-07 15:53 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 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 [this message] 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-7FiFkX6TpS@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).