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] Add an frange(type) constructor analogous to the irange version.
Date: Wed, 12 Oct 2022 08:50:47 +0200 [thread overview]
Message-ID: <20221012065050.412900-2-aldyh@redhat.com> (raw)
In-Reply-To: <20221012065050.412900-1-aldyh@redhat.com>
gcc/ChangeLog:
* value-range.h (frange::frange): Add constructor taking type.
---
gcc/value-range.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/gcc/value-range.h b/gcc/value-range.h
index 07a2067898c..9d630e40f78 100644
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -281,6 +281,7 @@ public:
frange ();
frange (const frange &);
frange (tree, tree, value_range_kind = VR_RANGE);
+ frange (tree type);
frange (tree type, const REAL_VALUE_TYPE &min, const REAL_VALUE_TYPE &max,
value_range_kind = VR_RANGE);
static bool supports_p (const_tree type)
@@ -1059,6 +1060,13 @@ frange::frange (const frange &src)
*this = src;
}
+inline
+frange::frange (tree type)
+{
+ m_discriminator = VR_FRANGE;
+ set_varying (type);
+}
+
// frange constructor from REAL_VALUE_TYPE endpoints.
inline
--
2.37.3
next prev parent reply other threads:[~2022-10-12 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 6:50 [COMMITTED] Add default relation_kind to floating point range-op entries Aldy Hernandez
2022-10-12 6:50 ` Aldy Hernandez [this message]
2022-10-12 6:50 ` [COMMITTED] Disable tree to bool conversion in frange::update_nan Aldy Hernandez
2022-10-12 6:50 ` [COMMITTED] Add method to query the sign of a NAN Aldy Hernandez
2022-10-12 6:50 ` [COMMITTED] Add stubs for floating point range-op tests 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=20221012065050.412900-2-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).