This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
- To: Robert Lipe <robertl at dgii dot com>
- Subject: Re: Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
- From: Mumit Khan <khan at xraylith dot wisc dot edu>
- Date: Mon, 01 Dec 1997 16:07:02 -0600
- Cc: Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>, egcs at cygnus dot com, Max Lawson <mlawson at drfmc dot ceng dot cea dot fr>, khan at xraylith dot wisc dot edu
Robert Lipe <robertl@dgii.com> writes:
>
> Perhaps there's some sort of slippery x86 thing going on here, becuase
> typename5.C fails on i586-pc-sco3.2v5.0.4, too. See:
> http://www.cygnus.com/ml/egcs/1997-Nov/0950.html
>
>
> Interestingly, it seems to be a recent failure.
>
> $ grep typename5.C */*.sum
> coff-971123/g++.sum:PASS: g++.pt/typename5.C (test for excess errors)
> coff-971129/g++.sum:FAIL: g++.pt/typename5.C (test for excess errors)
> elf-971123/g++.sum:PASS: g++.pt/typename5.C (test for excess errors)
> elf-971129/g++.sum:FAIL: g++.pt/typename5.C (test for excess errors)
>
To add another data point, see Alexandre Oliva's test results just posted.
He's getting lots of EH failures which points to the fact that he may be
using an old gas, yet *no* typename5.C failure.
This is certainly getting weird. fyi, I couldn't reproduce the problem on
any ix86 system I have access to -- linux-gnulibc1, cygwin32 and mingw32,
all running the same gas/binutils snapshot (binutils ss-971023).
Regards,
Mumit -- khan@xraylith.wisc.edu
http://www.xraylith.wisc.edu/~khan/