This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/17661] some invalid floating point values should be considered as "nan"
- From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 24 Aug 2015 09:52:27 +0000
- Subject: [Bug libc/17661] some invalid floating point values should be considered as "nan"
- Auto-submitted: auto-generated
- References: <bug-17661-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17661
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #10 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
As discussed, this is not a bug; glibc only aims that such trap representations
do not cause crashes, not that they are treated consistently as any particular
value. gnulib has been changed to agree:
commit bd38edc81714fc2679b02ef34033f9e15954d32f
Author: Paul Eggert <eggert@cs.ucla.edu>
Date: Fri Feb 20 18:09:47 2015 -0800
printf, isinf, etc.: noncanonical != NaN
Do not require that isinf, printf, etc. treat noncanonical
values as NaNs. Instead, require only that they do not crash.
[...]
--
You are receiving this mail because:
You are on the CC list for the bug.