public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	paolo@gcc.gnu.org, snyder@fnal.gov
Subject: Re: libstdc++/5875: operator<<(double) doesn't allow printing full precision (3.0 regression)
Date: Thu, 07 Mar 2002 16:38:00 -0000	[thread overview]
Message-ID: <20020308003824.8537.qmail@sources.redhat.com> (raw)

Synopsis: operator<<(double) doesn't allow printing full precision (3.0 regression)

Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Thu Mar  7 16:38:24 2002
Responsible-Changed-Why:
    Triaged.
State-Changed-From-To: open->analyzed
State-Changed-By: paolo
State-Changed-When: Thu Mar  7 16:38:24 2002
State-Changed-Why:
    Hi!
    I think your analysis is correct (as it was the first time,
    by the way ;-) and I would suggest posting directly the
    patch in the libstdc++ list. However, if you want to
    provide a testcase, you should do this as a patch against
    the concerned testsuite file, in the standard form based on
    the use of VERIFY, portable (this is the tricky point)
    across archs characterized by different machine precisions.
    I mean, do you think it would be safe testing:
    VERIFY(d - pi == 0.0) ??
    I don't think so. What do you suggest then?
    Ciao, Paolo.

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


             reply	other threads:[~2002-03-08  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 16:38 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-11 12:16 paolo
2002-03-08 12:16 Scott Snyder
2002-03-07 13:26 snyder

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=20020308003824.8537.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=snyder@fnal.gov \
    /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).