970917 on sparc-sun-solaris2.5.1: summary

[Joe Buck]

The gcc tests come out the same way as last time: 8 unexpected failures,
which is basically the same two tests failing with four different sets of
compiler options (compile/961203-1.c and execute/loop-2f.c).  All libio
and libstdc++ tests pass.

For g++ new things are happening.  First, the summary:

FAIL: g++.jason/operator.C overloaded (test for errors, line 13)
FAIL: g++.jason/operator.C overloaded (test for errors, line 14)
FAIL: g++.jason/template31.C (test for excess errors)
XPASS: g++.law/temps7.C (test for excess errors)
FAIL: g++.mike/eh16.C  Execution test
FAIL: g++.mike/eh17.C  Execution test
FAIL: g++.mike/p710.C previous declaration as.* (test for errors, line 32)
FAIL: g++.mike/p710.C .B::operator.*overloaded (test for errors, line 35)

		=== g++ Summary ===

# of expected passes		3315
# of unexpected failures	7
# of unexpected successes	1
# of expected failures		81
# of untested testcases		6
/remote/dtg103/jbuck/gnu/src/egcs-970917/gcc/testsuite/../xgcc \
version egcs-2.90.08 970917 (gcc2-970802 experimental)
----------------------

The jason/operator.C failures are the same as last time, so is the XPASS
and the p710.C failures.  eh16 and eh17 are new; I haven't studied them
in detail.  Some failures from last time are gone because libg++
dependencies have been cleaned up.

g++.jason/template31.C is a new failure.  It is most peculiar:
(the compilation flags are -ansi -pedantic-errors):

.../algobase.h: In function `class Component * __uninitialized_copy_aux(const class Component *, const class Component *, class Component *, struct __false_type)':
.../algobase.h:548: control reaches end of non-void function `__uninitialized_copy_aux(const Component *, const Component *, Component *, __false_type)'
.../vector.h: In method `class Component * vector<Component,__default_alloc_template<false,0> >::allocate_and_copy(unsigned int, const class Component *, const class Component *)':
.../vector.h:221: control reaches end of non-void function `vector<Component,__default_alloc_template<false,0> >::allocate_and_copy(unsigned int, const Component *, const Component *)'

Apparently reaching the end of a non-void function is treated as a pedwarn
(it turns to a warning when I just say -pedantic).
But both lines reported above are "throw;" lines -- this shouldn't be
confused with reaching the end of a non-void, since the end is *not*
reached.