Re: # of unexpected failures 768 ?

[Dennis Clarke <dclarke at blastwave dot org>]

>>> You need to look at the log to see what's going wrong, and run a few
>>> of the test cases.  There's probably a common cause.
>>
>> Also, on two different architectures I see similarly poor results. Here
>> are the sparc results :
>>
>> http://gcc.gnu.org/ml/gcc-testresults/2011-10/msg03531.html
>
> That's not the log, so there's no info.

no no .. thats just the summary. I have the full logs also.

> An ICE is always a bug.

That was what bothered me.

well, the first ice-cube in the log starts in the gcc tests thus :

                === gcc tests ===

Schedule of variations:
    unix

Running target unix
Using /opt/bw/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /opt/bw/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /opt/bw/src/GCC/gcc-4.6.2/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/opt/bw/src/GCC/gcc-4.6.2/gcc/testsuite/gcc.c-torture/compile/compile.exp
...
FAIL: gcc.c-torture/compile/limits-exprparen.c  -O0  (internal compiler
error)


the test that failed with ice was :

# Expect driver script for GCC Regression Tests
# Copyright (C) 1993, 1995, 1997, 2003, 2007 Free Software Foundation
#
# This file is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GCC; see the file COPYING3.  If not see
# <http://www.gnu.org/licenses/>.

# These tests come from Torbjorn Granlund's (tege@cygnus.com)
# C torture test suite, and other contributors.

# Load support procs.
load_lib gcc-dg.exp

# Initialize `dg'.
dg-init

# Main loop.
set saved-dg-do-what-default ${dg-do-what-default}
set dg-do-what-default "assemble"
gcc-dg-runtest [lsort [glob -nocomplain $srcdir/$subdir/*.\[cS\]]] "-w"
set dg-do-what-default ${saved-dg-do-what-default}

# All done.
dg-finish


Not too sure how to run that manually however here is the source of that
test :

# cat ../gcc-4.6.2/gcc/testsuite/gcc.c-torture/compile/limits-exprparen.c
#define LBR1 ( ( ( ( ( ( ( ( ( (
#define LBR2 LBR1 LBR1 LBR1 LBR1 LBR1 LBR1 LBR1 LBR1 LBR1 LBR1
#define LBR3 LBR2 LBR2 LBR2 LBR2 LBR2 LBR2 LBR2 LBR2 LBR2 LBR2
#define LBR4 LBR3 LBR3 LBR3 LBR3 LBR3 LBR3 LBR3 LBR3 LBR3 LBR3
#define LBR5 LBR4 LBR4 LBR4 LBR4 LBR4 LBR4 LBR4 LBR4 LBR4 LBR4
#define LBR6 LBR5 LBR5 LBR5 LBR5 LBR5 LBR5 LBR5 LBR5 LBR5 LBR5

#define RBR1 ) ) ) ) ) ) ) ) ) )
#define RBR2 RBR1 RBR1 RBR1 RBR1 RBR1 RBR1 RBR1 RBR1 RBR1 RBR1
#define RBR3 RBR2 RBR2 RBR2 RBR2 RBR2 RBR2 RBR2 RBR2 RBR2 RBR2
#define RBR4 RBR3 RBR3 RBR3 RBR3 RBR3 RBR3 RBR3 RBR3 RBR3 RBR3
#define RBR5 RBR4 RBR4 RBR4 RBR4 RBR4 RBR4 RBR4 RBR4 RBR4 RBR4
#define RBR6 RBR5 RBR5 RBR5 RBR5 RBR5 RBR5 RBR5 RBR5 RBR5 RBR5

int q5_var = LBR4 0 RBR4;


hrmm, that is a lot of parentheses !


Is there a log file somewhere that shows more detail on what blew up ?




-- 
--
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.       |
+-------------------------+-----------------------------------+