[Bug stdio/19853] Printing IBM long double in decimal with high precision is sometimes incorrect

cvs-commit at gcc dot gnu.org sourceware-bugzilla@sourceware.org
Thu Mar 31 17:17:00 GMT 2016


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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  37a4c70bd4c5c74ac562072e450dc02e8cb4c150 (commit)
      from  830566307f038387ca0af3fd327706a8d1a2f595 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=37a4c70bd4c5c74ac562072e450dc02e8cb4c150

commit 37a4c70bd4c5c74ac562072e450dc02e8cb4c150
Author: Paul E. Murphy <murphyp@linux.vnet.ibm.com>
Date:   Mon Feb 29 13:27:36 2016 -0600

    Increase internal precision of ldbl-128ibm decimal printf [BZ #19853]

    When the signs differ, the precision of the conversion sometimes
    drops below 106 bits.  This strategy is identical to the
    hexadecimal variant.

    I've refactored tst-sprintf3 to enable testing a value with more
    than 30 significant digits in order to demonstrate this failure
    and its solution.

    Additionally, this implicitly fixes a typo in the shift
    quantities when subtracting from the high mantissa to compute
    the difference.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                              |   14 ++++++++++++++
 stdio-common/tst-sprintf3.c            |   14 ++++++++++----
 sysdeps/ieee754/ldbl-128ibm/ldbl2mpn.c |   25 ++++++++++++++++++-------
 3 files changed, 42 insertions(+), 11 deletions(-)

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


More information about the Glibc-bugs mailing list