public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-372] Convert get_legacy_range in bounds_of_var_in_loop to irange API.
Date: Mon,  1 May 2023 06:33:58 +0000 (GMT)	[thread overview]
Message-ID: <20230501063358.77A4F383600B@sourceware.org> (raw)

https://gcc.gnu.org/g:2c39e0fabff4de3cedd82beb03b4e1987e273a33

commit r14-372-g2c39e0fabff4de3cedd82beb03b4e1987e273a33
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Wed Jan 25 12:59:50 2023 +0100

    Convert get_legacy_range in bounds_of_var_in_loop to irange API.
    
    gcc/ChangeLog:
    
            * vr-values.cc (bounds_of_var_in_loop): Convert to irange API.

Diff:
---
 gcc/vr-values.cc | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/gcc/vr-values.cc b/gcc/vr-values.cc
index 7f623102ac6..3d28198f9f5 100644
--- a/gcc/vr-values.cc
+++ b/gcc/vr-values.cc
@@ -331,13 +331,16 @@ bounds_of_var_in_loop (tree *min, tree *max, range_query *query,
 		      || initvr.undefined_p ())
 		    return false;
 
-		  tree initvr_min, initvr_max;
+		  tree initvr_type = initvr.type ();
+		  tree initvr_min = wide_int_to_tree (initvr_type,
+						      initvr.lower_bound ());
+		  tree initvr_max = wide_int_to_tree (initvr_type,
+						      initvr.upper_bound ());
 		  tree maxvr_type = maxvr.type ();
 		  tree maxvr_min = wide_int_to_tree (maxvr_type,
 						     maxvr.lower_bound ());
 		  tree maxvr_max = wide_int_to_tree (maxvr_type,
 						     maxvr.upper_bound ());
-		  get_legacy_range (initvr, initvr_min, initvr_max);
 
 		  /* Check if init + nit * step overflows.  Though we checked
 		     scev {init, step}_loop doesn't wrap, it is not enough

                 reply	other threads:[~2023-05-01  6:33 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:
  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=20230501063358.77A4F383600B@sourceware.org \
    --to=aldyh@gcc.gnu.org \
    --cc=gcc-cvs@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: 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).