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 r13-3196] Add frange::maybe_isnan (bool sign).
Date: Mon, 10 Oct 2022 12:50:59 +0000 (GMT)	[thread overview]
Message-ID: <20221010125059.34E483948A5E@sourceware.org> (raw)

https://gcc.gnu.org/g:e23f7dabe6f7ce1d92bfc07d2b62cc7bcdc0caae

commit r13-3196-ge23f7dabe6f7ce1d92bfc07d2b62cc7bcdc0caae
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Mon Oct 10 13:43:16 2022 +0200

    Add frange::maybe_isnan (bool sign).
    
    It is useful to know if there's the possiblity of a NAN with a given
    sign.  This is to complement maybe_isnan(void) which returns TRUE for a
    NAN of any sign.
    
    A follow-up patch implementing ABS will make use of this.
    
    gcc/ChangeLog:
    
            * value-range.h (frange::maybe_isnan): New.

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

diff --git a/gcc/value-range.h b/gcc/value-range.h
index 484f911bd90..07a2067898c 100644
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -323,6 +323,7 @@ public:
   bool known_isnan () const;
   bool known_isinf () const;
   bool maybe_isnan () const;
+  bool maybe_isnan (bool sign) const;
   bool maybe_isinf () const;
   bool signbit_p (bool &signbit) const;
 private:
@@ -1295,6 +1296,18 @@ frange::maybe_isnan () const
   return m_pos_nan || m_neg_nan;
 }
 
+// Return TRUE if range is possibly a NAN with SIGN.
+
+inline bool
+frange::maybe_isnan (bool sign) const
+{
+  if (undefined_p ())
+    return false;
+  if (sign)
+    return m_neg_nan;
+  return m_pos_nan;
+}
+
 // Return TRUE if range is a +NAN or -NAN.
 
 inline bool

                 reply	other threads:[~2022-10-10 12:50 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=20221010125059.34E483948A5E@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).