public inbox for
 help / color / mirror / Atom feed
From: Richard Biener <>
Subject: [PATCH 2/3] Less strip_offset in IVOPTs
Date: Wed, 21 Jun 2023 11:31:08 +0000 (UTC)	[thread overview]
Message-ID: <20230621113108.ZgpaqiBy53ghivBhiiO0bc_s_cPVaow26F6C-lXummc@z> (raw)

This avoids a strip_offset use in record_group_use where we know
it operates on addresses.

Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.

	* (record_group_use): Use
 gcc/ | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/ b/gcc/
index 7978c80b39e..65caf382bba 100644
--- a/gcc/
+++ b/gcc/
@@ -1175,9 +1175,6 @@ contain_complex_addr_expr (tree expr)
   return res;
-static tree
-strip_offset (tree expr, poly_uint64_pod *offset = nullptr);
 /* Allocates an induction variable with given initial value BASE and step STEP
    for loop LOOP.  NO_OVERFLOW implies the iv doesn't overflow.  */
@@ -1609,7 +1606,10 @@ record_group_use (struct ivopts_data *data, tree *use_p,
       unsigned int i;
-      addr_base = strip_offset (iv->base, &addr_offset);
+      gcc_assert (POINTER_TYPE_P (TREE_TYPE (iv->base)));
+      tree addr_toffset;
+      split_constant_offset (iv->base, &addr_base, &addr_toffset);
+      addr_offset = int_cst_value (addr_toffset);
       for (i = 0; i < data->vgroups.length (); i++)
 	  struct iv_use *use;

                 reply	other threads:[~2023-06-21 11:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230621113108.ZgpaqiBy53ghivBhiiO0bc_s_cPVaow26F6C-lXummc@z \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be 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).