This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug manual/21400] Section "Infinity and NaN" of the libc manual
- From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 20 Apr 2017 14:15:39 +0000
- Subject: [Bug manual/21400] Section "Infinity and NaN" of the libc manual
- Auto-submitted: auto-generated
- References: <bug-21400-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21400
--- Comment #2 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
(In reply to joseph@codesourcery.com from comment #1)
> Note that the full IEEE 754 semantics of fmin/fmax, including that sNaN
> maps to qNaN but qNaN arguments are ignored, are implemented in hardware
> on AArch64 at least (that is, the present functions can be implemented by
> a single instruction on AArch64).
https://www.gnu.org/savannah-checkouts/gnu/libc/manual/html_node/Infinity-and-NaN.html
says about the macro FE_SNANS_ALWAYS_SIGNAL:
"This macro, defined by TS 18661-1:2014, is defined to 1 in fenv.h to indicate
that functions and operations with signaling NaN inputs and floating-point
results always raise the invalid exception and return a quiet NaN, even in
cases (such as fmax, hypot and pow) where a quiet NaN input can produce a
non-NaN result."
So, if the hardware behaves differently, it should be noted.
--
You are receiving this mail because:
You are on the CC list for the bug.