This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Possible regression from gcc-3.0.x to gcc-3.2.x with std::setprecision
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Thu, 2 Jan 2003 14:43:13 -0600
- Subject: Re: Possible regression from gcc-3.0.x to gcc-3.2.x with std::setprecision
- References: <200212311113.gBVBDpf5006230@garfield.andypo.net>
> http://gcc.gnu.org/ml/libstdc++/2002-12/msg00064.html
>
>Basically, libstdc++ in v3.2 (and above), limits the maximum precision
>of a double to 16([1]) digits, whereas the constant
>
> std::numeric_limits<double>::min()
>
>needs 18 digits in order to write it out to a stream, and read it back
>from the stream to make it compare equal....
>
>gcc-3.0 limited the precision to 18([2]) digits....
>
>[1] std::numeric_limits<float, double>::digits10 + 1
>[2] std::numeric_limits<float, double>::digits10 + 3
This should be fixed. What you should do is make a self-contained test
case (as small as you can make it) and open a new GNATS report about
this.
thanks,
benjamin