From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26276 invoked by alias); 30 Oct 2011 23:28:33 -0000 Received: (qmail 26267 invoked by uid 22791); 30 Oct 2011 23:28:32 -0000 X-SWARE-Spam-Status: No, hits=1.3 required=5.0 tests=AWL,BAYES_50,GARBLED_SUBJECT,WEIRD_PORT X-Spam-Check-By: sourceware.org Received: from comm.purplecow.org (HELO comm.purplecow.org) (210.87.62.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 30 Oct 2011 23:28:13 +0000 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=iso-8859-1 Received: from interact.purplecow.org ([127.0.0.1]) by comm.purplecow.org (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPA id <0LTW00C4AJUWAU00@comm.purplecow.org> for gcc@gcc.gnu.org; Mon, 31 Oct 2011 10:28:08 +1100 (EST) Received: from interact.purplecow.org ([10.0.66.17] helo=interact.purplecow.org) with IPv4:25 by ASSP.nospam; Mon, 31 Oct 2011 10:28:08 +1100 Received: from 10.0.66.17 (proxying for unknown) (SquirrelMail authenticated user dclarke@blastwave.org) by interact.purplecow.org with HTTP; Sun, 30 Oct 2011 19:28:08 -0400 (EDT) Message-id: <50609.10.0.66.17.1320017288.squirrel@interact.purplecow.org> Date: Mon, 31 Oct 2011 09:28:00 -0000 Subject: # of unexpected failures 768 ? From: Dennis Clarke To: gcc@gcc.gnu.org Reply-to: dclarke@blastwave.org User-Agent: SquirrelMail/1.4.11 X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-10/txt/msg00543.txt.bz2 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. | +-------------------------+-----------------------------------+