public inbox for
help / color / mirror / Atom feed
From: Aldy Hernandez <>
Subject: [gcc r13-2893] Add an irange setter for wide_ints.
Date: Tue, 27 Sep 2022 08:46:35 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

commit r13-2893-g1db05e1a1c1ee3d8a95826d477173fb7c557c002
Author: Aldy Hernandez <>
Date:   Tue Sep 27 08:00:40 2022 +0200

    Add an irange setter for wide_ints.
    Just the same way as we have real_value setters for franges, we should
    have a wide_int version for irange.  This matches the irange
    constructor for wide_ints, and paves the way for the eventual
    conversion of irange to wide ints.
            * value-range.h (irange::set): New version taking wide_int_ref.

 gcc/value-range.h | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/gcc/value-range.h b/gcc/value-range.h
index 413e54bda6f..556e31aece1 100644
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -117,6 +117,8 @@ class GTY((user)) irange : public vrange
   // In-place setters.
   virtual void set (tree, tree, value_range_kind = VR_RANGE) override;
+  void set (tree type, const wide_int_ref &, const wide_int_ref &,
+	    value_range_kind = VR_RANGE);
   virtual void set_nonzero (tree type) override;
   virtual void set_zero (tree type) override;
   virtual void set_nonnegative (tree type) override;
@@ -687,6 +689,13 @@ irange::varying_compatible_p () const
   return true;
+inline void
+irange::set (tree type, const wide_int_ref &min, const wide_int_ref &max,
+	     value_range_kind kind)
+  set (wide_int_to_tree (type, min), wide_int_to_tree (type, max), kind);
 inline bool
 vrange::varying_p () const

                 reply	other threads:[~2022-09-27  8:46 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 \ \ \ \

* 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).