-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 2/26/2009 4:57 PM:
> I've done some investigation into failures of test-frexpl, test-isnanl, and
> test-vasnprintf-posix on Irix 6.5.
>
> So, I am working on a patch that looks for all instances of 0.0L / 0.0L in
> the
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 2/26/2009 6:13 PM:
>
> I removed the part of the test that should normally always fail:
> if (sprintf (buf, "%ls", wstring) != -1)
> return 2;
> because it does not fail on any known platform.
Actually, it DOES
Hi Eric,
> I'm now getting failures on Solaris 10, at the same line, and traced it to a
> call to the native:
>
> /* second byte uninitialized, and happens to be invalid character */
> wchar_t str[2] = { 'a', 0x65666768 };
> snprintf(buffer, 12, "%.*ls", 1, str);
>
> with a return of returns -1
Eric Blake wrote:
> > +static wchar_t wstring[] = { 'a', 'b', 'c', 0 };
>
> Are we guaranteed that on all platforms, 'a' promotes to L'a'? Or should
> we explicitly write the latter?
It is guaranteed: ISO C 99 paragraph 7.17.(2) says:
"wchar_t
... is an integer type whose range of values ca
I've done some investigation into failures of test-frexpl, test-isnanl, and
test-vasnprintf-posix on Irix 6.5.
The Irix 6.5 cc, on 0.0L/0.0L, produces:
(gdb) p sizeof x
$1 = 16
(gdb) x/4x &x
0x7ffb7ea0: 0x7ff7 0x 0x 0x
(gdb) p x
$2 = nan(0x7
Bruno Haible clisp.org> writes:
>
> Thanks for these findings! It's not only "%.*ls" which has the bug, but also
> "%ls" without a precision. I'm applying this workaround:
>
>
> 2009-02-26 Bruno Haible clisp.org>
>
> Fix *printf behaviour regarding the %ls directive.
I'm now getting
I encountered a weird build failure on a Solaris machine:
checking random.h usability... no
checking random.h presence... yes
configure: WARNING: random.h: present but cannot be compiled
configure: WARNING: random.h: check for missing prerequisite headers?
configure: WARNING: random.h: see the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 2/26/2009 4:54 AM:
>
> Thanks for these findings! It's not only "%.*ls" which has the bug, but also
> "%ls" without a precision. I'm applying this workaround:
>
> +static wchar_t wstring[] = { 'a', 'b', 'c', 0 };
Are we
Hi Gary,
> > $ grep NEED config.h
>
> % grep NEED lib/config.h
> #define NEED_PRINTF_DIRECTIVE_A 1
> #define NEED_PRINTF_DIRECTIVE_F 1
> /* #undef NEED_PRINTF_DOUBLE */
> /* #undef NEED_PRINTF_ENOMEM */
> /* #undef NEED_PRINTF_FLAG_GROUPING */
> #define NEED_PRINTF_FLAG_LEFTADJUST 1
> #define NEE
