public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "no.1zhouzhonghua at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug stdio/13726] New: the result of  wprintf (L"%La\n", (long double) 22.625); is 0xb.bp+1, but the correct result should be 0xb.5p+1
Date: Thu, 23 Feb 2012 03:33:00 -0000	[thread overview]
Message-ID: <bug-13726-131@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13726
           Summary: the result of  wprintf (L"%La\n", (long double)
                    22.625); is 0xb.bp+1, but the correct result should be
                    0xb.5p+1
           Product: glibc
           Version: 2.14
            Status: NEW
          Severity: normal
          Priority: P2
         Component: stdio
        AssignedTo: unassigned@sourceware.org
        ReportedBy: no.1zhouzhonghua@163.com
    Classification: Unclassified


in the file sysdeps/x86_64/fpu/printf_fphex.c there is one expression in line
60:
leading = *numstr++;
but i think is should be like this :
 leading = *numstr++;                            \
 ++wnumstr;                                     \

-- 
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-02-23  3:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  3:33 no.1zhouzhonghua at 163 dot com [this message]
2012-02-23 10:51 ` [Bug stdio/13726] " aj at suse dot de
2012-02-23 12:47 ` polacek at redhat dot com
2012-02-24  8:14 ` no.1zhouzhonghua at 163 dot com
2012-02-29 15:36 ` polacek at redhat dot com
2012-03-04 15:56 ` polacek at redhat dot com
2012-03-06 21:17 ` polacek at redhat dot com
2014-06-26 15:19 ` 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-13726-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).