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 r12-1088] Use get_range_query in simplify_conversion_using_ranges.
Date: Thu, 27 May 2021 08:49:42 +0000 (GMT)	[thread overview]
Message-ID: <20210527084942.CFDC7385040E@sourceware.org> (raw)

https://gcc.gnu.org/g:22137a3db85bee83c92cf23ba36fe0d08364afc2

commit r12-1088-g22137a3db85bee83c92cf23ba36fe0d08364afc2
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Thu May 27 10:43:11 2021 +0200

    Use get_range_query in simplify_conversion_using_ranges.
    
    Before the fix to the ranger dependency chain yesterday (commit
    7f0cfeb1) I thought an ICE I was seeing was due to my get_range_query
    patchet.  This was not the case, but this small change crept in while I
    was debugging the failure.
    
    I'm reverting the change as was approved.
    
    Tested on x86-64 Linux.
    
    gcc/ChangeLog:
    
            * vr-values.c (simplify_conversion_using_ranges): Use
            get_range_query instead of get_global_range_query.

Diff:
---
 gcc/vr-values.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/vr-values.c b/gcc/vr-values.c
index d283108b7c2..3d0be8edb3b 100644
--- a/gcc/vr-values.c
+++ b/gcc/vr-values.c
@@ -3837,7 +3837,7 @@ simplify_conversion_using_ranges (gimple_stmt_iterator *gsi, gimple *stmt)
   value_range vr;
   if (!INTEGRAL_TYPE_P (TREE_TYPE (innerop)))
     return false;
-  get_global_range_query ()->range_of_expr (vr, innerop, stmt);
+  get_range_query (cfun)->range_of_expr (vr, innerop, stmt);
   if (vr.undefined_p () || vr.varying_p ())
     return false;
   innermin = widest_int::from (vr.lower_bound (), TYPE_SIGN (TREE_TYPE (innerop)));


                 reply	other threads:[~2021-05-27  8:49 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=20210527084942.CFDC7385040E@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).