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-3245] Add method to query the sign of a NAN.
Date: Wed, 12 Oct 2022 06:51:39 +0000 (GMT)	[thread overview]
Message-ID: <20221012065139.A7A7C384D157@sourceware.org> (raw)

https://gcc.gnu.org/g:658788f3480e95f1dda0a143b60be89099e5d3c7

commit r13-3245-g658788f3480e95f1dda0a143b60be89099e5d3c7
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Tue Oct 11 19:21:14 2022 +0200

    Add method to query the sign of a NAN.
    
    In writing some range-op entries I noticed we don't have a way to
    query the sign of the NAN in a range, unless the range only contains
    NAN, in which case you can just use frange::signbit_p.  This patch
    adds a method that returns TRUE if there exists the possiblity of a
    NAN and we know its sign.
    
    gcc/ChangeLog:
    
            * value-range.h (frange::nan_signbit_p): New.

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

diff --git a/gcc/value-range.h b/gcc/value-range.h
index cb5e9d0522c..60b989b2b50 100644
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -328,6 +328,7 @@ public:
   bool maybe_isnan (bool sign) const;
   bool maybe_isinf () const;
   bool signbit_p (bool &signbit) const;
+  bool nan_signbit_p (bool &signbit) const;
 private:
   void verify_range ();
   bool normalize_kind ();
@@ -1358,4 +1359,20 @@ frange::signbit_p (bool &signbit) const
   return false;
 }
 
+// If range has a NAN with a known sign, set it in SIGNBIT and return
+// TRUE.
+
+inline bool
+frange::nan_signbit_p (bool &signbit) const
+{
+  if (undefined_p ())
+    return false;
+
+  if (m_pos_nan == m_neg_nan)
+    return false;
+
+  signbit = m_neg_nan;
+  return true;
+}
+
 #endif // GCC_VALUE_RANGE_H

                 reply	other threads:[~2022-10-12  6:51 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=20221012065139.A7A7C384D157@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).