public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: axiong@ca.ibm.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, paolo@gcc.gnu.org
Subject: Re: libstdc++/9548: 64-bit copiling/linking: incorrect results from setf(ios::fixed) or precision(-1)
Date: Mon, 03 Feb 2003 23:41:00 -0000	[thread overview]
Message-ID: <20030203234149.26381.qmail@sources.redhat.com> (raw)

Synopsis: 64-bit copiling/linking: incorrect results from setf(ios::fixed) or precision(-1)

Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Mon Feb  3 23:41:49 2003
Responsible-Changed-Why:
    Fixing.
State-Changed-From-To: open->analyzed
State-Changed-By: paolo
State-Changed-When: Mon Feb  3 23:41:49 2003
State-Changed-Why:
    According to 22.2.2.2.2 p11, if (flags & fixed) != 0 then
    str.precision() is specified in the conversion
    specification, even when str.precision is <= 0. Admittedly,
    this is quite a weird situation, which triggers a bug
    in the current library: it prepares a "%.*f" format
    but then calls snprintf without passing the precision field.
    
    Instead of fixing the bug, I'm going to implement the
    resolution of DR231, which is in the "Ready" state:
    according to it str.precision is simply _always_ specified
    in the conversion specification.
    
    Thanks for your report,
    Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9548


             reply	other threads:[~2003-02-03 23:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 23:41 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 18:26 axiong
2003-02-03 18:16 axiong

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=20030203234149.26381.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=axiong@ca.ibm.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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).