On Mon, Jan 12, 2009 at 06:55:17AM -0700, Eric Blake wrote:
> According to Eric Blake on 1/9/2009 7:50 PM:
> > But so far, I've discovered this
> > about -0.0L on Irix 6.2:
> >
> > With 'cc -n32', LDBL_MIN is a compile-time constant; but with 'gc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 1/9/2009 7:50 PM:
> But so far, I've discovered this
> about -0.0L on Irix 6.2:
>
> With 'cc -n32', LDBL_MIN is a compile-time constant; but with 'gcc', I get
> an error when trying t
cc, and I get another failure (for -0.0L)
> with CC="cc -O".
>
> Can you debug this a bit?
I'm still looking into the NaN issue. But so far, I've discovered this
about -0.0L on Irix 6.2:
With 'cc -n32', LDBL_MIN is a compile-time constant; but with 'gcc&
Eric Blake wrote:
> > In the
> > 'double' case on mingw, in 'e' format, we need to use 3 digits for the
> > exponent, to match what MSVCRT does. This is not needed for 'long double' -
> > since 'long double' output is not supported by MSVCRT in the first place.)
>
> Actually, in the latest version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 9/18/2008 4:34 AM:
> (You apparently copied the code for 'double'.
Yes.
> In the
> 'double' case on mingw, in 'e' format, we need to use 3 digits for the
> exponent, to match what MSVCRT does. This is not needed for 'long
Eric Blake wrote:
> with both pieces in place, I've tested that Irix 5.3
> passes the testsuite. So here's what I'm pushing:
>
> From: Eric Blake <[EMAIL PROTECTED]>
> Date: Tue, 16 Sep 2008 09:36:24 -0600
> Subject: [PATCH] vasnprintf: support Irix 5.3
>
> * lib/vasnprintf.c (VASNPRINTF): Also
Bruno Haible clisp.org> writes:
> > > the system sprintf does not know how to print -0, so the result is
> > > 0.00 and lacks -. Does it make more sense to adjust the existing
> > > gl_PRINTF_INFINITE_LONG_DOUBLE (which also tests for NaN) to add a test
> > > for negative zero, or to add a n
