From: Aldy Hernandez <aldyh@redhat.com>
To: GCC patches <gcc-patches@gcc.gnu.org>
Subject: [COMMITTED] Call set_undefined from irange constructor.
Date: Fri, 29 Apr 2022 11:02:33 +0200 [thread overview]
Message-ID: <20220429090236.718140-2-aldyh@redhat.com> (raw)
In-Reply-To: <20220429090236.718140-1-aldyh@redhat.com>
Small clean up to use set_undefined instead of duplicating the
functionality therein.
Tested on x86-64 Linux.
gcc/ChangeLog:
* value-range.h (irange::irange): Use set_undefined.
---
gcc/value-range.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/gcc/value-range.h b/gcc/value-range.h
index fe7795b55a6..b64e02426ca 100644
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -397,9 +397,8 @@ inline
irange::irange (tree *base, unsigned nranges)
{
m_base = base;
- m_num_ranges = 0;
m_max_ranges = nranges;
- m_kind = VR_UNDEFINED;
+ set_undefined ();
}
// Constructors for int_range<>.
--
2.35.1
next prev parent reply other threads:[~2022-04-29 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 9:02 [COMMITTED] Make irange::intersect(wide_int, wide_int) private Aldy Hernandez
2022-04-29 9:02 ` Aldy Hernandez [this message]
2022-04-29 9:02 ` [COMMITTED] Prefer global range info setters that take a range Aldy Hernandez
2022-04-29 9:02 ` [COMMITTED] Remove various deprecated methods in class irange Aldy Hernandez
2022-04-29 9:02 ` [COMMITTED] Move common code from range-op.cc to header files Aldy Hernandez
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=20220429090236.718140-2-aldyh@redhat.com \
--to=aldyh@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).