Bruno Haible wrote:
You can also try a standalone test program, linked against the system's
sprintf(), like this:
===
#include
int main()
{
char buf[100];
sprintf (buf, "%Lf", -0.0L);
printf ("%s\n", buf);
return 0;
}
===
The resu
Tom G. Christensen wrote:
> > Thanks, that's good so far. The interesting stuff is to look
> > - what happens in line vasnprintf.c:2734,
> >
> Single stepping from test-vasprintf-posix:1305 does not seem to stop
> there (closest is 2531)
>
> > - at the result in line vasnprintf.c:4635.
> >
Bruno Haible wrote:
Thanks, that's good so far. The interesting stuff is to look
- what happens in line vasnprintf.c:2734,
>
Single stepping from test-vasprintf-posix:1305 does not seem to stop
there (closest is 2531)
- at the result in line vasnprintf.c:4635.
>
Single stepping indeed m
Bruno Haible wrote:
Tom G. Christensen wrote:
I see the same test failure when building m4-1.4.11 on Irix 5.3 and 6.2
regardless of compiler used.
Irix 6.2 with MIPSpro 7.3.0 or GCC 4.3.0 (Indigo2 R10K):
test-vasprintf-posix.c:1309: assertion failed
/bin/ksh[9]: 10221 Abort(coredump)
FAIL: test
Bruno Haible wrote:
Eric Blake wrote, citing Nelson Beebe:
|
| Machinetype:SGI O2 R1-SC (150 MHz);IRIX 6.5
| Configure environment: CC=c89 CXX=CC CFLAGS=-I/usr/local/include
CXXFLAGS=-I/usr/local/includ
Tom G. Christensen wrote:
> > - Does 1.0 / -0.0 < 0 evaluate to true or false?
> > - Does 1.0L / -0.0L < 0 evaluate to true or false?
> true
> true
Thanks. That's different from what I got on some IRIX 6.5 machine, but
it's consistent with what you and Nelson see.
> > - At test-vaspr
Tom G. Christensen wrote:
> I see the same test failure when building m4-1.4.11 on Irix 5.3 and 6.2
> regardless of compiler used.
>
> Irix 6.2 with MIPSpro 7.3.0 or GCC 4.3.0 (Indigo2 R10K):
> test-vasprintf-posix.c:1309: assertion failed
> /bin/ksh[9]: 10221 Abort(coredump)
> FAIL: test-vasprint
Eric Blake wrote, citing Nelson Beebe:
> |
> | Machinetype:SGI O2 R1-SC (150 MHz);IRIX 6.5
> | Configure environment: CC=c89 CXX=CC CFLAGS=-I/usr/local/include
> CXXFLAGS=-I/usr/local/include LDFLAGS=-Wl,-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 4/3/2008 8:01 PM:
| |
| | FAIL: test-fseeko.sh
|
| Not much detail on the failure there. I guess we could improve
| test-fseeko.c to do better line number reporting. Can you please run
| test-fseeko in a debugger to see wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 4/3/2008 10:15 PM:
|
| You would not need to write this stereotypic reply if the main tests were
| run before the gnulib ones:
Ah, but then if an m4 test fails, the gnulib tests don't get run. I can't
win.
But I'll prob
Hi Eric,
Eric Blake wrote:
> The failures are all in gnulib portability code,
> and don't appear to immediately impact m4 behavior (the gnulib
> replacements are more general than what m4 uses them for). Meanwhile, can
> you please rerun with 'make -k' to get the full set of failures?
You would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Nelson H. F. Beebe on 4/3/2008 3:53 PM:
| I've just built and installed m4-1.4.11 on most machines in our test
| lab of about 20 flavors of Unix covering most major CPU architectures.
Thanks for the feedback. The failures are all in gnu
12 matches
Mail list logo
