public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: GCC patches <gcc-patches@gcc.gnu.org>
Cc: Andrew MacLeod <amacleod@redhat.com>, Aldy Hernandez <aldyh@redhat.com>
Subject: [COMMITTED] Inline irange::set_nonzero.
Date: Mon,  1 May 2023 08:29:06 +0200	[thread overview]
Message-ID: <20230501062906.564803-12-aldyh@redhat.com> (raw)
In-Reply-To: <20230501062906.564803-1-aldyh@redhat.com>

irange::set_nonzero is used everywhere and benefits immensely from
inlining.

gcc/ChangeLog:

	* value-range.h (irange::set_nonzero): Inline.
---
 gcc/value-range.h | 20 ++++++++++++++++++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/gcc/value-range.h b/gcc/value-range.h
index 9a834c91b17..5cff50e6d03 100644
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -886,8 +886,24 @@ irange::upper_bound () const
 inline void
 irange::set_nonzero (tree type)
 {
-  wide_int zero = wi::zero (TYPE_PRECISION (type));
-  set (type, zero, zero, VR_ANTI_RANGE);
+  unsigned prec = TYPE_PRECISION (type);
+
+  if (TYPE_UNSIGNED (type))
+    {
+      m_type = type;
+      m_kind = VR_RANGE;
+      m_base[0] = wi::one (prec);
+      m_base[1] = m_nonzero_mask = wi::minus_one (prec);
+      m_num_ranges = 1;
+
+      if (flag_checking)
+	verify_range ();
+    }
+  else
+    {
+      wide_int zero = wi::zero (prec);
+      set (type, zero, zero, VR_ANTI_RANGE);
+    }
 }
 
 // Set value range VR to a ZERO range of type TYPE.
-- 
2.40.0


      parent reply	other threads:[~2023-05-01  6:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01  6:28 [COMMITTED] vrange_storage overhaul Aldy Hernandez
2023-05-01  6:28 ` [COMMITTED] Remove irange::{min,max,kind} Aldy Hernandez
2023-05-01  6:28 ` [COMMITTED] Remove irange::tree_{lower,upper}_bound Aldy Hernandez
2023-05-01  6:28 ` [COMMITTED] Various cleanups in vr-values.cc towards ranger API Aldy Hernandez
2023-05-01  6:28 ` [COMMITTED] Convert get_legacy_range in bounds_of_var_in_loop to irange API Aldy Hernandez
2023-05-01  6:29 ` [COMMITTED] Merge irange::union/intersect into irange_union/intersect Aldy Hernandez
2023-05-01  6:29 ` [COMMITTED] Conversion to irange wide_int API Aldy Hernandez
2023-05-01  6:29 ` [COMMITTED] Replace vrp_val* with wide_ints Aldy Hernandez
2023-05-01  6:29 ` [COMMITTED] Rewrite bounds_of_var_in_loop() to use ranges Aldy Hernandez
2023-05-01  6:29 ` [COMMITTED] Convert internal representation of irange to wide_ints Aldy Hernandez
2023-05-01  6:29 ` [COMMITTED] Cleanup irange::set Aldy Hernandez
2023-05-01  6:29 ` Aldy Hernandez [this message]

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=20230501062906.564803-12-aldyh@redhat.com \
    --to=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@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).