public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14046] New: strtof returns incorrectly-rounded results
Date: Wed, 02 May 2012 02:07:00 -0000	[thread overview]
Message-ID: <bug-14046-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14046

             Bug #: 14046
           Summary: strtof returns incorrectly-rounded results
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: unassigned@sourceware.org
        ReportedBy: bugdal@aerifal.cx
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


Test case:

"0.000000000000000000000000000000000000000000002101947696487225606385594374934874196920392912814773657635602425834686624028790902229957282543182373046875"

This is the decimal value of 0x1.8p-149, the value exactly halfway between the
smallest two positive single-precision floating point values. It has more than
DECIMAL_DIG significant digits, so it should round as follows:

"If the subject sequence D has the decimal form and more than DECIMAL_DIG
significant digits, consider the two bounding, adjacent decimal strings L and
U, both having DECIMAL_DIG significant digits, such that the values of L, D,
and U satisfy L <= D <= U. The result should be one of the (equal or adjacent)
values that would be obtained by correctly rounding L and U according to the
current rounding direction, with the extra stipulation that the error with
respect to D should have a correct sign for the current rounding direction."

Here L="0.00000000000000000000000000000000000000000000210194769648722560638"
and U="0.00000000000000000000000000000000000000000000210194769648722560639".
Correctly rounded, they should be 0x1p-149 and 0x1p-148, respectively, but
strtof rounds all three (D,L,U) to 0x1p-149.

This is just the particular case I thought to check; surely there are many
others, possibly without even going into the denormal range (which was the
first place I thought to look for bugs).

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-05-02  2:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  2:07 bugdal at aerifal dot cx [this message]
2012-05-02 10:01 ` [Bug libc/14046] " jsm28 at gcc dot gnu.org
2014-06-25 11:09 ` fweimer at redhat 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-14046-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).