public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: egcs-971127: testsuite results on i586-pc-linux-gnulibc1
@ 1997-12-01  2:36 Max Lawson
  1997-12-01  7:38 ` Theodore Papadopoulo
  0 siblings, 1 reply; 6+ messages in thread
From: Max Lawson @ 1997-12-01  2:36 UTC (permalink / raw)
  To: khan; +Cc: egcs

> From khan@eh_pc11.xraylith.wisc.edu Fri Nov 28 22:00 MET 1997
> 
> Max Lawson <mlawson@drfmc.ceng.cea.fr> writes:
> > 
> > 	=> typename5.C is still failing. That was the case in the 
> > previous snapshot. I've added the log. Case ...
> > 
> 
> I don't see the error on my system (RH 4.1, libc 5.3.12), and I didn't
> see it for the last snapshot either.
> 

I'm using libc5.4.39. I've noticed that several testsuite results have been 
posted for  ix86-glibc1 systems with different issues for the typename5.C 
test...

> You might want to compile it by hand with -v option and post that.
> Hopefully something will turn up. You don't perchance have environment
> variables like LIBRARY_PATH defined, do you?

I've only assigned "/tmp/egcs-xxxxxx/libraries/libstdc++" to LD_LIBRARY_PATH 
as suggested to avoid the failure of EH tests when checking a not-yet-installed 
snapshot.

> 
> Mumit
> 

Here is the compiler output with the -v option on:

Reading specs from ../specs
gcc version egcs-2.90.19 971127 (gcc2-970802 experimental)
 ../cpp -lang-c++ -v -I/tmp/egcs-971127/libio -I/tmp/egcs-971127/libraries/libio -I/tmp/egcs-971127/libstdc++ -I/tmp/egcs-971127/libstdc++/stl -I../ -isystem ../include -undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -D__GNUC_MINOR__=90 -trigraphs -D__STRICT_ANSI__ -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem(posix) -D__EXCEPTIONS -pedantic-errors -Di386 -Di586 -Asystem(unix) -Acpu(i386) -Amachine(i386) -D__i386__ -D__i586__ -Asystem(unix) -Acpu(i386) -Amachine(i386) g++.old-deja/g++.pt/typename5.C /tmp/cca26353.ii
GNU CPP version egcs-2.90.19 971127 (gcc2-970802 experimental) (i386 Linux/ELF)
#include "..." search starts here:
#include <...> search starts here:
 /tmp/egcs-971127/libio
 /tmp/egcs-971127/libraries/libio
 /tmp/egcs-971127/libstdc++
 /tmp/egcs-971127/libstdc++/stl
 ..
 ../include
 /usr/local/include/g++
 /usr/local/include
 /usr/local/i586-pc-linux-gnulibc1/include
 /usr/local/lib/gcc-lib/i586-pc-linux-gnulibc1/egcs-2.90.19/include
 /usr/include
End of search list.
 ../cc1plus /tmp/cca26353.ii -quiet -dumpbase typename5.cc -pedantic-errors -ansi -version -o /tmp/cca26353.s
GNU C++ version egcs-2.90.19 971127 (gcc2-970802 experimental) (i586-pc-linux-gnulibc1) compiled by GNU C version egcs-2.90.19 971127 (gcc2-970802 experimental).
g++.old-deja/g++.pt/typename5.C:25: prototype for `void C<U>::Func(U)' does not match any in class `C<U>'
g++.old-deja/g++.pt/typename5.C:19: candidate is: void C<U>::Func(typename B<U>::A_Type)
g++.old-deja/g++.pt/typename5.C: In method `void C<U>::Func(U)':
g++.old-deja/g++.pt/typename5.C:25: template definition of non-template `void C<U>::Func(U)'



Regards, Max

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: egcs-971127: testsuite results on i586-pc-linux-gnulibc1
  1997-12-01  2:36 egcs-971127: testsuite results on i586-pc-linux-gnulibc1 Max Lawson
@ 1997-12-01  7:38 ` Theodore Papadopoulo
  1997-12-01 11:03   ` Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1] Mumit Khan
  0 siblings, 1 reply; 6+ messages in thread
From: Theodore Papadopoulo @ 1997-12-01  7:38 UTC (permalink / raw)
  To: khan; +Cc: egcs

> 
> Max Lawson <mlawson@drfmc.ceng.cea.fr> writes:
> > 
> > 	=> typename5.C is still failing. That was the case in the 
> > previous snapshot. I've added the log. Case ...
> > 
> 
> I don't see the error on my system (RH 4.1, libc 5.3.12), and I didn't
> see it for the last snapshot either.
> 

	Mummit,

From the other reports I see, you seem more to be the exception than
the average case or maybe your are the only one with RH4.1 which seems
unlikely.

I also have:

XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
XPASS: g++.mike/dyncast1.C  Execution test
XPASS: g++.mike/dyncast2.C  Execution test
FAIL: g++.pt/typename5.C (test for excess errors)
 
=== g++ Summary ===

# of expected passes            3399
# of unexpected failures        1
# of unexpected successes       3
# of expected failures          80
# of untested testcases         6
/0/robotvis/papadop/gcc/egcs/egcs-971127/gcc/testsuite/../xgcc version egcs-2.90.19 971127 (gcc2-970802 experimental)


My system is Slackware based with a kernel Linux 2.0.29. with two libs
/lib/libc.so.4.7.6 and /lib/libc.so.5.3.12. As for binutils, I'm
using binutils-2.8.1.0.15.tar.gz but I cannot install them so that I'm
just putting the directory binutils into the egcs-971127. I assume this
works as exception handling works fine !!

	Theo.


--------------------------------------------------------------------
Theodore Papadopoulo
Email:  papadop@sophia.inria.fr               Tel: (33) 93 65 76 01
--------------------------------------------------------------------

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
  1997-12-01  7:38 ` Theodore Papadopoulo
@ 1997-12-01 11:03   ` Mumit Khan
  1997-12-01 11:33     ` Robert Lipe
  0 siblings, 1 reply; 6+ messages in thread
From: Mumit Khan @ 1997-12-01 11:03 UTC (permalink / raw)
  To: Theodore Papadopoulo; +Cc: egcs, Max Lawson

On Mon, 1 Dec 1997, Theodore Papadopoulo wrote:

> From the other reports I see, you seem more to be the exception than
> the average case or maybe your are the only one with RH4.1 which seems
> unlikely.
> 

Nope, I'm not the only one. See 

    http://www.cygnus.com/ml/egcs/1997-Nov/0946.html          

for the results from Peter Schmid, posted on Nov. 29. He also does not see
the failure for typename5.C that you see. Max Lawson's message that shows 
the error message from running the compiler on typename5.C just doesn't
happen on my machine.

Mumit



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
  1997-12-01 11:03   ` Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1] Mumit Khan
@ 1997-12-01 11:33     ` Robert Lipe
  1997-12-01 19:30       ` Mumit Khan
  0 siblings, 1 reply; 6+ messages in thread
From: Robert Lipe @ 1997-12-01 11:33 UTC (permalink / raw)
  To: Mumit Khan; +Cc: Theodore Papadopoulo, egcs, Max Lawson

> > From the other reports I see, you seem more to be the exception than
> > the average case or maybe your are the only one with RH4.1 which seems
> 
> for the results from Peter Schmid, posted on Nov. 29. He also does not see
> the failure for typename5.C that you see. Max Lawson's message that shows 


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)



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
  1997-12-01 11:33     ` Robert Lipe
@ 1997-12-01 19:30       ` Mumit Khan
  0 siblings, 0 replies; 6+ messages in thread
From: Mumit Khan @ 1997-12-01 19:30 UTC (permalink / raw)
  To: Robert Lipe; +Cc: Theodore Papadopoulo, egcs, Max Lawson, khan

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/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
@ 1997-12-01 17:20 Max Lawson
  0 siblings, 0 replies; 6+ messages in thread
From: Max Lawson @ 1997-12-01 17:20 UTC (permalink / raw)
  To: robertl, khan; +Cc: Theodore.Papadopoulo, egcs

	Maybe, we should post assembly and/or preprocessed outputs for 
a given test-case compiled with given options. This way s.o. :-) could 
have a look... Could s.o. post an adequate test ?

Regards, Max
 

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~1997-12-01 19:30 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-12-01  2:36 egcs-971127: testsuite results on i586-pc-linux-gnulibc1 Max Lawson
1997-12-01  7:38 ` Theodore Papadopoulo
1997-12-01 11:03   ` Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1] Mumit Khan
1997-12-01 11:33     ` Robert Lipe
1997-12-01 19:30       ` Mumit Khan
1997-12-01 17:20 Max Lawson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).