public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-28322-131-l6B8poang5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28322-131@http.sourceware.org/bugzilla/>

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

--- 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 
integers larger than 64 bits (given the use of strtoull), when _Float128 
(long double on some architectures) has 111 payload bits and arguably 
strings corresponding to all possible 111-bit payloads should be parsed 
(so requiring adding code to glibc to handle parsing strings to 128-bit 
integers for this purpose - including on some architectures that don't 
have __int128 support).  That leads to the question of whether that oddity 
should be documented, or considered as a bug (or both).

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

  parent reply	other threads:[~2021-09-09 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 12:21 [Bug math/28322] New: " arthur200126 at gmail dot com
2021-09-09 13:55 ` [Bug math/28322] " arthur200126 at gmail dot com
2021-09-09 14:02 ` arthur200126 at gmail dot com
2021-09-09 17:09 ` joseph at codesourcery dot com [this message]
2021-09-11 11:41 ` arthur200126 at gmail dot com
2021-09-11 11:57 ` arthur200126 at gmail dot com

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=bug-28322-131-l6B8poang5@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).