> -Original Message-
> From: Mike Stump [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 28, 2007 6:47 PM
> To: [EMAIL PROTECTED]
> Cc: gcc@gcc.gnu.org
> Subject: Re: how to start using gcc on windows
>
> On Apr 28, 2007, at 5:03 PM, [EMAIL PROTECTED] wrote:
> > I have looked hard, bu
[EMAIL PROTECTED] wrote:
On Apr 29, 2007, at 1:01 PM, Tim Prince wrote:
It makes no sense at all for sqrt() to break down with change in
precision mode.
If you do an extended-precision (80-bit) sqrt and then round the result
again to a double (64-bit) then those two roundings will incre
On Apr 29, 2007, at 1:01 PM, Tim Prince wrote:
[EMAIL PROTECTED] wrote:
I just (re-)discovered these tables giving maximum known errors in
some libm functions when extended precision is enabled:
http://people.inf.ethz.ch/gonnet/FPAccuracy/linux/summary.html
and when the precision of the man
> I noted in the GCC docs (see for example http://gcc.gnu.org/
> onlinedocs/gcc/Interoperation.html) that we have the following text
> in the section "Known Causes of Trouble with GCC":
>
> > On Ultrix, the Fortran compiler expects registers 2 through 5 to be
> > saved by function calls. Howe
[EMAIL PROTECTED] wrote:
I just (re-)discovered these tables giving maximum known errors in some
libm functions when extended precision is enabled:
http://people.inf.ethz.ch/gonnet/FPAccuracy/linux/summary.html
and when the precision of the mantissa is set to 53 bits (double
precision):
Richard Henderson wrote:
On Tue, Apr 03, 2007 at 10:56:42AM +0200, Uros Bizjak wrote:
> ... Note that a change of default precision control may
> affect the results returned by some of the mathematical functions.
>
> to the documentation to warn users about this fact.
Eh. It can seriously bre
I noted in the GCC docs (see for example http://gcc.gnu.org/
onlinedocs/gcc/Interoperation.html) that we have the following text
in the section "Known Causes of Trouble with GCC":
On Ultrix, the Fortran compiler expects registers 2 through 5 to be
saved by function calls. However, the C comp
