# of unexpected failures 768 ?

[Dennis Clarke]

I'm not too sure how many things changed from 4.6.1 to 4.6.2 but I am
seeing a really large increase in the number of "unexpected failures" on
various tests.

With 4.6.1 and Solaris I was able to get reasonable results :

http://gcc.gnu.org/ml/gcc-testresults/2011-07/msg00139.html

Then if I use the resultant compiler from a 4.6.1 build I get a massive
increase in failures on both i386 and Sparc :

http://gcc.gnu.org/ml/gcc-testresults/2011-10/msg03286.html

and thus far on Sparc I see :

                === gcc Summary ===

# of expected passes            69236
# of unexpected failures        768
# of expected failures          235
# of unresolved testcases       1
# of unsupported tests          1240
/opt/bw/src/GCC/gcc-4.6.2-SunOS5.8-sparc/gcc/xgcc  version 4.6.2
(Blastwave.org Inc Thu Oct 27 11:33:20 GMT 2011)

and :

                === g++ Summary ===

# of expected passes            26251
# of unexpected failures        101
# of unexpected successes       1
# of expected failures          169
# of unresolved testcases       1
# of unsupported tests          496
/opt/bw/src/GCC/gcc-4.6.2-SunOS5.8-sparc/gcc/testsuite/g++/../../g++ 
version 4.6.2 (Blastwave.org Inc Thu Oct 27 11:33:20 GMT 2011)

This seems blatantly wrong. At what point does one throw out the result of
a bootstrap as not-acceptable ? With any non-zero value for "unexpected
failures" ?

Also, I see bucket loads of these :

FAIL: g++.dg/pch/wchar-1.C  -O2 -g -I. (internal compiler error)

What should I think about an "internal compiler error" ?

Dennis
( concerned in Solaris world )



-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke           | Solaris and Linux and Open Source |
| dclarke@blastwave.org   | Respect for open standards.       |
+-------------------------+-----------------------------------+