From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id C1BFC385AC3D; Thu,  9 Sep 2021 17:09:03 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C1BFC385AC3D
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/28322] Specify parsing of nan?
Date: Thu, 09 Sep 2021 17:09:03 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: math
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-28322-131-l6B8poang5@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28322-131@http.sourceware.org/bugzilla/>
References: <bug-28322-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2021 17:09:03 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D28322

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery =
dot com> ---
Note the oddity that the parsing of NaN payloads from strings can't handle=
=20
integers larger than 64 bits (given the use of strtoull), when _Float128=20
(long double on some architectures) has 111 payload bits and arguably=20
strings corresponding to all possible 111-bit payloads should be parsed=20
(so requiring adding code to glibc to handle parsing strings to 128-bit=20
integers for this purpose - including on some architectures that don't=20
have __int128 support).  That leads to the question of whether that oddity=
=20
should be documented, or considered as a bug (or both).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=