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 g:a0b1798042d033fd2cc2c806afbb77875dd2909b Date: Thu, 29 Feb 2024 18:15:08 +0000 [thread overview] Message-ID: <bug-114151-4-spKaVLtk4p@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 #5 from Andrew Macleod <amacleod at redhat dot com> --- (In reply to rguenther@suse.de from comment #4) > > What was definitely missing is consideration of POLY_INT_CSTs (and > variable polys, as I think there's no range info for those). > Ranger doesn't do anything with POLY_INTs, mostly because I didn't understand them. > We do eventually want to improve how ranger behaves here. I'm not sure > why when we do not provide a context 'stmt' it can't see to compute > a range valid at the SSA names point of definition? (so basically > compute the global range) The call looks like it doesn't provide the stmt. Without the stmt, all ranger will ever provide is global ranges. I think you are asking why, If there is no global range, it doesn't try to compute one from the ssa_name_def_stmt? Ranger does when it is active. Otherwise it simply picks up the global information from SSA_NAME_RANGE_INFO() Of course, if its a poly int, we don't actually support those... so all you will ever see is VARYING. Again, because I don't understand them. > Maybe there's another API to do that. But I thought it was convenient > to use range_of_expr as that also handles GENERIC expression trees > to some extent and those are common within SCEV. A range can always be calculated by simply calling fold_range from gimple-range-fold.h: // Fold stmt S into range R using range query Q. bool fold_range (vrange &r, gimple *s, range_query *q = NULL); if range_query is not provided, it'll simply use the current one. If you want to ensure its only global ranges, you call it with fold_range (r, SSA_NAME_DEF_STMT (name), get_global_range_query ());
next prev parent reply other threads:[~2024-02-29 18:15 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 13:57 [Bug tree-optimization/114151] New: " 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 [this message] 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 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-spKaVLtk4p@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).