From: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>
To: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCHv2][Ping 1] Increase internal precision of ldbl-128ibm decimal printf
Date: Thu, 31 Mar 2016 17:18:00 -0000 [thread overview]
Message-ID: <56FD5BF4.5040301@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1603302302550.773@digraph.polyomino.org.uk>
Thanks Joseph. Committed as 37a4c70bd4c5c74ac562072e450dc02e8cb4c150.
On 03/30/2016 06:04 PM, Joseph Myers wrote:
> This patch is OK.
>
> It's arguable how different this bug actually is from 5268 (the original
> submission of bug 5268 doesn't clearly define the scope of the bug, and
> the one-bit-loss issue here gets mentioned later in the bug 5268
> comments). But I suppose this bug can be considered more specific to the
> one-bit-loss, with 5268 left for the more general case where there are
> more than 106 bits of precision in the long double value.
>
prev parent reply other threads:[~2016-03-31 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 22:41 [PATCHv2] " Paul E. Murphy
2016-03-21 23:29 ` Joseph Myers
2016-03-22 14:16 ` Paul E. Murphy
2016-03-30 15:14 ` [PATCHv2][Ping 1] " Paul E. Murphy
2016-03-30 23:05 ` Joseph Myers
2016-03-31 17:18 ` Paul E. Murphy [this message]
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=56FD5BF4.5040301@linux.vnet.ibm.com \
--to=murphyp@linux.vnet.ibm.com \
--cc=libc-alpha@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).