* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
@ 2007-08-30 18:23 ` michelin60 at gmail dot com
2007-08-30 18:35 ` Andrew Pinski
2007-08-30 18:24 ` dberlin at dberlin dot org
` (14 subsequent siblings)
15 siblings, 1 reply; 20+ messages in thread
From: michelin60 at gmail dot com @ 2007-08-30 18:23 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from michelin60 at gmail dot com 2007-08-30 18:23 -------
Did not work as attachment with the following message:
GCC Bugzilla has suffered an internal error. Please save this page and send it
to dberlin@gcc.gnu.org with details of what you were doing at the time this
message appeared.
URL: http://gcc.gnu.org/bugzilla/attachment.cgi
undef error - Undefined subroutine Fh::slice at
data/template/template/en/default/global/hidden-fields.html.tmpl line 58
Sending the make log below:
make[1]: Entering directory `/var/tmp/43/build-156'
make[2]: Entering directory `/var/tmp/43/build-156/fixincludes'
autogen -T ../../gcc-4.3.0/fixincludes/check.tpl
../../gcc-4.3.0/fixincludes/inclhack.def
autogen: symbol lookup error: autogen: undefined symbol: gh_enter
make[2]: [check] Error 127 (ignored)
/bin/sh ./check.sh ../../gcc-4.3.0/fixincludes/tests/base
/bin/sh: ./check.sh: No such file or directory
make[2]: [check] Error 127 (ignored)
make[2]: Leaving directory `/var/tmp/43/build-156/fixincludes'
make[2]: Entering directory `/var/tmp/43/build-156/intl'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/var/tmp/43/build-156/intl'
make[2]: Entering directory `/var/tmp/43/build-156/libcpp'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/var/tmp/43/build-156/libcpp'
make[2]: Entering directory `/var/tmp/43/build-156/libdecnumber'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/var/tmp/43/build-156/libdecnumber'
make[2]: Entering directory `/var/tmp/43/build-156/libiberty'
make[3]: Entering directory `/var/tmp/43/build-156/libiberty/testsuite'
powerpc-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -g -O2 -I..
-I../../../gcc-4.3.0/libiberty/testsuite/../../include -o test-demangle \
../../../gcc-4.3.0/libiberty/testsuite/test-demangle.c
../libiberty.a
make[2]: Entering directory `/var/tmp/43/build-156/gcc'
Making a new config file...
echo "set tmpdir /var/tmp/43/build-156/gcc/testsuite" >> ./tmp0
test -d testsuite || mkdir testsuite
test -d testsuite/gcc || mkdir testsuite/gcc
(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd ../../gcc-4.3.0/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
cd testsuite/gcc; \
rm -f tmp-site.exp; \
sed '/set tmpdir/ s|testsuite|testsuite/gcc|' \
< ../../site.exp > tmp-site.exp; \
/bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ;
\
export TCL_LIBRARY ; fi ; \
GCC_EXEC_PREFIX="/usr/lib/gcc/" ; export GCC_EXEC_PREFIX ; \
runtest --tool gcc )
WARNING: Couldn't find the global config file.
Test Run By root on Thu Aug 30 10:13:23 2007
Native configuration is powerpc-unknown-linux-gnu
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /var/tmp/43/gcc-4.3.0/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/compile/compile.exp
...
powerpc-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -g -O2 -I..
-I../../../gcc-4.3.0/libiberty/testsuite/../../include -DHAVE_CONFIG_H -I.. -o
test-pexecute \
../../../gcc-4.3.0/libiberty/testsuite/test-pexecute.c
../libiberty.a
powerpc-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -g -O2 -I..
-I../../../gcc-4.3.0/libiberty/testsuite/../../include -DHAVE_CONFIG_H -I.. -o
test-expandargv \
../../../gcc-4.3.0/libiberty/testsuite/test-expandargv.c
../libiberty.a
./test-demangle < ../../../gcc-4.3.0/libiberty/testsuite/demangle-expected
./test-demangle: 765 tests, 0 failures
./test-pexecute
./test-expandargv
PASS: test-expandargv-0.
PASS: test-expandargv-1.
PASS: test-expandargv-2.
PASS: test-expandargv-3.
make[3]: Leaving directory `/var/tmp/43/build-156/libiberty/testsuite'
make[2]: Leaving directory `/var/tmp/43/build-156/libiberty'
make[2]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
Making check in include
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include'
if [ ! -d "./powerpc-unknown-linux-gnu/bits/stdc++.h.gch" ]; then \
mkdir -p ./powerpc-unknown-linux-gnu/bits/stdc++.h.gch; \
fi; \
/var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
-B/var/tmp/43/build-156/./gcc -nostdinc++
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
-B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
-isystem /usr/powerpc-unknown-linux-gnu/include -isystem
/usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
c++-header -g -O2 -D_GNU_SOURCE
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
-I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O0 -g
/var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdc++.h -o
powerpc-unknown-linux-gnu/bits/stdc++.h.gch/O0g.gch
touch ./powerpc-unknown-linux-gnu/bits/stdc++.h
if [ ! -d "./powerpc-unknown-linux-gnu/bits/stdc++.h.gch" ]; then \
mkdir -p ./powerpc-unknown-linux-gnu/bits/stdc++.h.gch; \
fi; \
/var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
-B/var/tmp/43/build-156/./gcc -nostdinc++
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
-B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
-isystem /usr/powerpc-unknown-linux-gnu/include -isystem
/usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
c++-header -g -O2 -D_GNU_SOURCE
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
-I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O2 -g
/var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdc++.h -o
powerpc-unknown-linux-gnu/bits/stdc++.h.gch/O2g.gch
touch ./powerpc-unknown-linux-gnu/bits/stdc++.h
if [ ! -d "./powerpc-unknown-linux-gnu/bits/stdtr1c++.h.gch" ]; then \
mkdir -p ./powerpc-unknown-linux-gnu/bits/stdtr1c++.h.gch; \
fi; \
/var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
-B/var/tmp/43/build-156/./gcc -nostdinc++
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
-B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
-isystem /usr/powerpc-unknown-linux-gnu/include -isystem
/usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
c++-header -g -O2 -D_GNU_SOURCE
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
-I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O2 -g
/var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdtr1c++.h -o
powerpc-unknown-linux-gnu/bits/stdtr1c++.h.gch/O2g.gch
/var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdtr1c++.h:34:25:
warning:
/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu/bits/stdc++.h.gch/O0g.gch:
not used because `__NO_INLINE__' not defined
touch ./powerpc-unknown-linux-gnu/bits/stdtr1c++.h
if [ ! -d "./powerpc-unknown-linux-gnu/bits/extc++.h.gch" ]; then \
mkdir -p ./powerpc-unknown-linux-gnu/bits/extc++.h.gch; \
fi; \
/var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
-B/var/tmp/43/build-156/./gcc -nostdinc++
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
-L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
-B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
-isystem /usr/powerpc-unknown-linux-gnu/include -isystem
/usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
c++-header -g -O2 -D_GNU_SOURCE
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
-I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
-I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O2 -g
/var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/extc++.h -o
powerpc-unknown-linux-gnu/bits/extc++.h.gch/O2g.gch
touch ./powerpc-unknown-linux-gnu/bits/extc++.h
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include'
Making check in libsupc++
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libsupc++'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libsupc++'
Making check in libmath
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libmath'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libmath'
Making check in src
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src'
Making check in po
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/po'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/po'
Making check in testsuite
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
make -j1 check-DEJAGNU
make[4]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
make[4]: warning: -jN forced in submake: disabling jobserver mode.
Making a new site.exp file...
srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd
../../../../gcc-4.3.0/libstdc++-v3/testsuite && pwd`; export srcdir; \
EXPECT=expect; export EXPECT; \
runtest=runtest; \
if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
l='libstdc++'; for tool in $l; do \
$runtest --tool $tool --srcdir $srcdir ; \
done; \
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
fi
WARNING: Couldn't find the global config file.
Test Run By root on Thu Aug 30 10:14:08 2007
Native configuration is powerpc-unknown-linux-gnu
=== libstdc++ tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
ERROR: tcl error sourcing
/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp.
ERROR: could not compile testsuite_abi.cc
while executing
"error "could not compile $f""
(procedure "v3-build_support" line 57)
invoked from within
"v3-build_support"
(file "/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp"
line 22)
invoked from within
"source /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Running
/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
ERROR: tcl error sourcing
/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp.
ERROR: could not compile testsuite_abi.cc
while executing
"error "could not compile $f""
(procedure "v3-build_support" line 57)
invoked from within
"v3-build_support"
(file
"/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp"
line 25)
invoked from within
"source
/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
=== libstdc++ Summary ===
make[4]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
true "AR_FLAGS=rc" "CC_FOR_BUILD=powerpc-unknown-linux-gnu-gcc"
"CC_FOR_TARGET=/var/tmp/43/build-156/./gcc/xgcc -B/var/tmp/43/build-156/./gcc/
-B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
-isystem /usr/powerpc-unknown-linux-gnu/include -isystem
/usr/powerpc-unknown-linux-gnu/sys-include" "CFLAGS=-O2 -g -O2 " "CXXFLAGS=-g
-O2 -D_GNU_SOURCE" "CFLAGS_FOR_BUILD=-g -O2" "CFLAGS_FOR_TARGET=-O2 -g -O2 "
"INSTALL=/usr/bin/ginstall -c" "INSTALL_DATA=/usr/bin/ginstall -c -m 644"
"INSTALL_PROGRAM=/usr/bin/ginstall -c" "INSTALL_SCRIPT=/usr/bin/ginstall -c"
"LDFLAGS=" "LIBCFLAGS=-O2 -g -O2 " "LIBCFLAGS_FOR_TARGET=-O2 -g -O2 "
"MAKE=make" "MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000 "
"PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "RUNTESTFLAGS="
"exec_prefix=/usr" "infodir=/usr/share/info" "libdir=/usr/lib"
"includedir=/usr/include" "prefix=/usr"
"tooldir=/usr/powerpc-unknown-linux-gnu"
"gxx_include_dir=/usr/include/c++/4.3.0"
"AR=/usr/powerpc-unknown-linux-gnu/bin/ar" "AS=/var/tmp/43/build-156/./gcc/as"
"LD=/var/tmp/43/build-156/./gcc/collect-ld"
"RANLIB=/usr/powerpc-unknown-linux-gnu/bin/ranlib"
"NM=/var/tmp/43/build-156/./gcc/nm" "NM_FOR_BUILD="
"NM_FOR_TARGET=/usr/powerpc-unknown-linux-gnu/bin/nm" "DESTDIR=" "WERROR="
DO=all multi-do # make
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
make[2]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
test -d testsuite || mkdir testsuite
test -d testsuite/g++ || mkdir testsuite/g++
(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd ../../gcc-4.3.0/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
cd testsuite/g++; \
rm -f tmp-site.exp; \
sed '/set tmpdir/ s|testsuite|testsuite/g++|' \
< ../../site.exp > tmp-site.exp; \
/bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ;
\
export TCL_LIBRARY ; fi ; \
GCC_EXEC_PREFIX="/usr/lib/gcc/" ; export GCC_EXEC_PREFIX ; \
runtest --tool g++ )
WARNING: Couldn't find the global config file.
Test Run By root on Thu Aug 30 10:14:52 2007
Native configuration is powerpc-unknown-linux-gnu
=== g++ tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /var/tmp/43/gcc-4.3.0/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/bprob/bprob.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/charset/charset.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/compat/compat.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/compat/struct-layout-1.exp
...
WARNING: Could not compile g++.dg/compat/struct-layout-1 generator
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/debug/debug.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/debug/dwarf2/dwarf2.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/dg.exp ...
FAIL: g++.dg/conversion/simd1.C (test for warnings, line 8)
FAIL: g++.dg/eh/simd-3.C execution test
FAIL: g++.dg/ext/attribute-test-1.C (test for warnings, line 10)
FAIL: g++.dg/ext/attribute-test-2.C (test for warnings, line 14)
FAIL: g++.dg/ext/attribute-test-3.C (test for warnings, line 26)
FAIL: g++.dg/ext/attribute-test-4.C (test for warnings, line 26)
XPASS: g++.dg/tree-ssa/copyprop-1.C scan-tree-dump-not .* = [^>;]*;
FAIL: g++.dg/warn/Wall-write-strings.C (test for warnings, line 5)
FAIL: g++.dg/warn/write-strings-default.C (test for warnings, line 6)
FAIL: g++.dg/warn/write-strings.C (test for warnings, line 6)
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/gcov/gcov.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/gomp/gomp.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/pch/pch.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/special/ecos.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/tls/tls.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/torture/dg-torture.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/tree-prof/tree-prof.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/vect/vect.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.old-deja/old-deja.exp ...
=== g++ Summary ===
# of expected passes 16394
# of unexpected failures 9
# of unexpected successes 1
# of expected failures 87
# of unsupported tests 114
/var/tmp/43/build-156/gcc/testsuite/g++/../../g++ version 4.3.0 20070830
(experimental) (GCC)
make[2]: [check-g++] Error 1 (ignored)
make[2]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
make check-am
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
true DO=all multi-do # make
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
make[2]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
test -d testsuite || mkdir testsuite
test -d testsuite/gfortran || mkdir testsuite/gfortran
(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd ../../gcc-4.3.0/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
cd testsuite/gfortran; \
rm -f tmp-site.exp; \
sed '/set tmpdir/ s|testsuite|testsuite/gfortran|' \
< ../../site.exp > tmp-site.exp; \
/bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ;
\
export TCL_LIBRARY ; fi ; \
GCC_EXEC_PREFIX="/usr/lib/gcc/" ; export GCC_EXEC_PREFIX ; \
runtest --tool gfortran )
WARNING: Couldn't find the global config file.
Test Run By root on Thu Aug 30 10:56:12 2007
Native configuration is powerpc-unknown-linux-gnu
=== gfortran tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /var/tmp/43/gcc-4.3.0/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/dg.exp ...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/execute.exp
...
FAIL: gfortran.dg/fmt_p_1.f90 -O0 execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O1 execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O2 execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -g execution test
FAIL: gfortran.dg/fmt_p_1.f90 -Os execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O0 execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O1 execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O2 execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -g execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -Os execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O1 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O2 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -g execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -Os execution test
FAIL: gcc.c-torture/execute/mayalias-2.c compilation, -O3 -g (internal
compiler error)
FAIL: gcc.c-torture/execute/mayalias-3.c compilation, -O3 -g (internal
compiler error)
FAIL: gfortran.dg/nint_2.f90 -O0 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O0 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O1 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O2 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer execution
test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -g execution test
FAIL: gfortran.dg/output_exponents_1.f90 -Os execution test
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/unsorted/unsorted.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/charset/charset.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/compat/compat.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp
...
WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/cpp/cpp.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/cpp/trad/trad.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/debug/debug.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf2.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/dfp/dfp.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/dg.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/gomp/gomp.exp ...
FAIL: gcc.dg/20051207-3.c (test for errors, line 7)
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/vect/vect.exp ...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
...
FAIL: gcc.dg/builtins-61.c scan-tree-dump return 0.0
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
...
FAIL: gcc.dg/memcpy-1.c scan-tree-dump-times nasty_local 0
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/format/format.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/gomp/gomp.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/ipa/ipa.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/matrix/matrix.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/noncompile/noncompile.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/pch/pch.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/special/mips-abi.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/special/special.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/tls/tls.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/torture/dg-torture.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/tree-prof/tree-prof.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/tree-ssa/tree-ssa.exp ...
=== gfortran Summary ===
# of expected passes 20760
# of unexpected failures 33
# of expected failures 8
# of unsupported tests 36
/var/tmp/43/build-156/gcc/testsuite/gfortran/../../gfortran version 4.3.0
20070830 (experimental) (GCC)
make[2]: [check-gfortran] Error 1 (ignored)
make[2]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty'
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty/testsuite'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty/testsuite'
make[2]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty'
make[2]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
Making check in testsuite
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
make check-DEJAGNU
make[4]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
Making a new site.exp file...
srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd
../../../../gcc-4.3.0/libgomp/testsuite && pwd`; export srcdir; \
EXPECT=expect; export EXPECT; \
runtest=runtest; \
if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
l='libgomp'; for tool in $l; do \
$runtest --tool $tool --srcdir $srcdir ; \
done; \
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
fi
WARNING: Couldn't find the global config file.
Test Run By root on Thu Aug 30 12:33:47 2007
Native configuration is powerpc-unknown-linux-gnu
=== libgomp tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /var/tmp/43/gcc-4.3.0/libgomp/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /var/tmp/43/gcc-4.3.0/libgomp/testsuite/libgomp.c/c.exp ...
Running /var/tmp/43/gcc-4.3.0/libgomp/testsuite/libgomp.c++/c++.exp ...
XPASS: gcc.dg/tree-ssa/update-threading.c scan-tree-dump-times Invalid sum 0
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/i386/i386-costmodel-vect.exp
...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/ppc/ppc-costmodel-vect.exp
...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/spu/spu-costmodel-vect.exp
...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/x86_64/x86_64-costmodel-vect.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/vect.exp ...
Running /var/tmp/43/gcc-4.3.0/libgomp/testsuite/libgomp.fortran/fortran.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vmx/vmx.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vxworks/vxworks.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/weak/weak.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/acker1.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/arm-isr.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/bprob.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/dectest.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/dhry.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/gcov.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/i386-prefetch.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/linkage.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/matrix1.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/mg-2.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/mg.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/options.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/sieve.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/sort2.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/alpha/alpha.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/arm/arm.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/arm/neon/neon.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/bfin/bfin.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/cris/cris.exp ...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/cris/torture/cris-torture.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/frv/frv.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/i386/i386.exp ...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/i386/math-torture/math-torture.exp
...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/ia64/ia64.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/m68k/m68k.exp ...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/mips/inter/mips16-inter.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/mips/mips.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/powerpc/powerpc.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/s390/s390.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/sh/sh.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/sparc/sparc.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/spu/spu.exp ...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/x86_64/abi/abi-x86_64.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/xstormy16/xstormy16.exp
...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.test-framework/test-framework.exp ...
skipping test framework tests, CHECK_TEST_FRAMEWORK is not defined
=== gcc Summary ===
# of expected passes 46252
# of unexpected failures 5
# of unexpected successes 1
# of expected failures 171
# of unresolved testcases 2
# of untested testcases 35
# of unsupported tests 366
/var/tmp/43/build-156/gcc/xgcc version 4.3.0 20070830 (experimental) (GCC)
make[2]: [check-gcc] Error 1 (ignored)
make[2]: Leaving directory `/var/tmp/43/build-156/gcc'
=== libgomp Summary ===
# of expected passes 1607
make[4]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
make[3]: Entering directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
true DO=all multi-do # make
make[3]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
make[2]: Leaving directory
`/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
make[1]: Leaving directory `/var/tmp/43/build-156'
--
michelin60 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dberlin at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:23 ` [Bug fortran/33252] " michelin60 at gmail dot com
@ 2007-08-30 18:35 ` Andrew Pinski
0 siblings, 0 replies; 20+ messages in thread
From: Andrew Pinski @ 2007-08-30 18:35 UTC (permalink / raw)
To: gcc-bugzilla; +Cc: gcc-bugs
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp.
> ERROR: could not compile testsuite_abi.cc
This was fixed by:
2007-08-30 Jakub Jelinek <jakub@redhat.com>
PR target/33168
* config/rs6000/rs6000.c (rs6000_elf_in_small_data_p): Return
true if any of the compare_section_name calls returned true,
rather than if any returned false.
Try again after that patch.
Thanks,
Andrew Pinski
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
2007-08-30 18:23 ` [Bug fortran/33252] " michelin60 at gmail dot com
@ 2007-08-30 18:24 ` dberlin at dberlin dot org
2007-08-30 18:35 ` pinskia at gmail dot com
` (13 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: dberlin at dberlin dot org @ 2007-08-30 18:24 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from dberlin at gcc dot gnu dot org 2007-08-30 18:24 -------
Subject: Re: GCC-4.3.0 Bootstrap testsuite error increase
Log in before submitting the attachment
On 30 Aug 2007 18:23:23 -0000, michelin60 at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #1 from michelin60 at gmail dot com 2007-08-30 18:23 -------
> Did not work as attachment with the following message:
>
> GCC Bugzilla has suffered an internal error. Please save this page and send it
> to dberlin@gcc.gnu.org with details of what you were doing at the time this
> message appeared.
>
> URL: http://gcc.gnu.org/bugzilla/attachment.cgi
> undef error - Undefined subroutine Fh::slice at
> data/template/template/en/default/global/hidden-fields.html.tmpl line 58
>
> Sending the make log below:
>
> make[1]: Entering directory `/var/tmp/43/build-156'
> make[2]: Entering directory `/var/tmp/43/build-156/fixincludes'
> autogen -T ../../gcc-4.3.0/fixincludes/check.tpl
> ../../gcc-4.3.0/fixincludes/inclhack.def
> autogen: symbol lookup error: autogen: undefined symbol: gh_enter
> make[2]: [check] Error 127 (ignored)
> /bin/sh ./check.sh ../../gcc-4.3.0/fixincludes/tests/base
> /bin/sh: ./check.sh: No such file or directory
> make[2]: [check] Error 127 (ignored)
> make[2]: Leaving directory `/var/tmp/43/build-156/fixincludes'
> make[2]: Entering directory `/var/tmp/43/build-156/intl'
> make[2]: Nothing to be done for `check'.
> make[2]: Leaving directory `/var/tmp/43/build-156/intl'
> make[2]: Entering directory `/var/tmp/43/build-156/libcpp'
> make[2]: Nothing to be done for `check'.
> make[2]: Leaving directory `/var/tmp/43/build-156/libcpp'
> make[2]: Entering directory `/var/tmp/43/build-156/libdecnumber'
> make[2]: Nothing to be done for `check'.
> make[2]: Leaving directory `/var/tmp/43/build-156/libdecnumber'
> make[2]: Entering directory `/var/tmp/43/build-156/libiberty'
> make[3]: Entering directory `/var/tmp/43/build-156/libiberty/testsuite'
> powerpc-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -g -O2 -I..
> -I../../../gcc-4.3.0/libiberty/testsuite/../../include -o test-demangle \
> ../../../gcc-4.3.0/libiberty/testsuite/test-demangle.c
> ../libiberty.a
> make[2]: Entering directory `/var/tmp/43/build-156/gcc'
> Making a new config file...
> echo "set tmpdir /var/tmp/43/build-156/gcc/testsuite" >> ./tmp0
> test -d testsuite || mkdir testsuite
> test -d testsuite/gcc || mkdir testsuite/gcc
> (rootme=`${PWDCMD-pwd}`; export rootme; \
> srcdir=`cd ../../gcc-4.3.0/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
> cd testsuite/gcc; \
> rm -f tmp-site.exp; \
> sed '/set tmpdir/ s|testsuite|testsuite/gcc|' \
> < ../../site.exp > tmp-site.exp; \
> /bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
> EXPECT=expect ; export EXPECT ; \
> if [ -f ${rootme}/../expect/expect ] ; then \
> TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ;
> \
> export TCL_LIBRARY ; fi ; \
> GCC_EXEC_PREFIX="/usr/lib/gcc/" ; export GCC_EXEC_PREFIX ; \
> runtest --tool gcc )
> WARNING: Couldn't find the global config file.
> Test Run By root on Thu Aug 30 10:13:23 2007
> Native configuration is powerpc-unknown-linux-gnu
>
> === gcc tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using /var/tmp/43/gcc-4.3.0/gcc/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/compile/compile.exp
> ...
> powerpc-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -g -O2 -I..
> -I../../../gcc-4.3.0/libiberty/testsuite/../../include -DHAVE_CONFIG_H -I.. -o
> test-pexecute \
> ../../../gcc-4.3.0/libiberty/testsuite/test-pexecute.c
> ../libiberty.a
> powerpc-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -g -O2 -I..
> -I../../../gcc-4.3.0/libiberty/testsuite/../../include -DHAVE_CONFIG_H -I.. -o
> test-expandargv \
> ../../../gcc-4.3.0/libiberty/testsuite/test-expandargv.c
> ../libiberty.a
> ./test-demangle < ../../../gcc-4.3.0/libiberty/testsuite/demangle-expected
> ./test-demangle: 765 tests, 0 failures
> ./test-pexecute
> ./test-expandargv
> PASS: test-expandargv-0.
> PASS: test-expandargv-1.
> PASS: test-expandargv-2.
> PASS: test-expandargv-3.
> make[3]: Leaving directory `/var/tmp/43/build-156/libiberty/testsuite'
> make[2]: Leaving directory `/var/tmp/43/build-156/libiberty'
> make[2]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
> Making check in include
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include'
> if [ ! -d "./powerpc-unknown-linux-gnu/bits/stdc++.h.gch" ]; then \
> mkdir -p ./powerpc-unknown-linux-gnu/bits/stdc++.h.gch; \
> fi; \
> /var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
> -B/var/tmp/43/build-156/./gcc -nostdinc++
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
> -B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
> -isystem /usr/powerpc-unknown-linux-gnu/include -isystem
> /usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
> c++-header -g -O2 -D_GNU_SOURCE
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
> -I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O0 -g
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdc++.h -o
> powerpc-unknown-linux-gnu/bits/stdc++.h.gch/O0g.gch
> touch ./powerpc-unknown-linux-gnu/bits/stdc++.h
> if [ ! -d "./powerpc-unknown-linux-gnu/bits/stdc++.h.gch" ]; then \
> mkdir -p ./powerpc-unknown-linux-gnu/bits/stdc++.h.gch; \
> fi; \
> /var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
> -B/var/tmp/43/build-156/./gcc -nostdinc++
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
> -B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
> -isystem /usr/powerpc-unknown-linux-gnu/include -isystem
> /usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
> c++-header -g -O2 -D_GNU_SOURCE
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
> -I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O2 -g
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdc++.h -o
> powerpc-unknown-linux-gnu/bits/stdc++.h.gch/O2g.gch
> touch ./powerpc-unknown-linux-gnu/bits/stdc++.h
> if [ ! -d "./powerpc-unknown-linux-gnu/bits/stdtr1c++.h.gch" ]; then \
> mkdir -p ./powerpc-unknown-linux-gnu/bits/stdtr1c++.h.gch; \
> fi; \
> /var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
> -B/var/tmp/43/build-156/./gcc -nostdinc++
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
> -B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
> -isystem /usr/powerpc-unknown-linux-gnu/include -isystem
> /usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
> c++-header -g -O2 -D_GNU_SOURCE
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
> -I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O2 -g
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdtr1c++.h -o
> powerpc-unknown-linux-gnu/bits/stdtr1c++.h.gch/O2g.gch
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/stdtr1c++.h:34:25:
> warning:
> /var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu/bits/stdc++.h.gch/O0g.gch:
> not used because `__NO_INLINE__' not defined
> touch ./powerpc-unknown-linux-gnu/bits/stdtr1c++.h
> if [ ! -d "./powerpc-unknown-linux-gnu/bits/extc++.h.gch" ]; then \
> mkdir -p ./powerpc-unknown-linux-gnu/bits/extc++.h.gch; \
> fi; \
> /var/tmp/43/build-156/./gcc/xgcc -shared-libgcc
> -B/var/tmp/43/build-156/./gcc -nostdinc++
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src
> -L/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs
> -B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
> -isystem /usr/powerpc-unknown-linux-gnu/include -isystem
> /usr/powerpc-unknown-linux-gnu/sys-include -Winvalid-pch -Wno-deprecated -x
> c++-header -g -O2 -D_GNU_SOURCE
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu
> -I/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include
> -I/var/tmp/43/gcc-4.3.0/libstdc++-v3/libsupc++ -O2 -g
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/include/precompiled/extc++.h -o
> powerpc-unknown-linux-gnu/bits/extc++.h.gch/O2g.gch
> touch ./powerpc-unknown-linux-gnu/bits/extc++.h
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/include'
> Making check in libsupc++
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libsupc++'
> make[3]: Nothing to be done for `check'.
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libsupc++'
> Making check in libmath
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libmath'
> make[3]: Nothing to be done for `check'.
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/libmath'
> Making check in src
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src'
> make[3]: Nothing to be done for `check'.
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/src'
> Making check in po
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/po'
> make[3]: Nothing to be done for `check'.
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/po'
> Making check in testsuite
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
> make -j1 check-DEJAGNU
> make[4]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
> make[4]: warning: -jN forced in submake: disabling jobserver mode.
> Making a new site.exp file...
> srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd
> ../../../../gcc-4.3.0/libstdc++-v3/testsuite && pwd`; export srcdir; \
> EXPECT=expect; export EXPECT; \
> runtest=runtest; \
> if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
> l='libstdc++'; for tool in $l; do \
> $runtest --tool $tool --srcdir $srcdir ; \
> done; \
> else echo "WARNING: could not find \`runtest'" 1>&2; :;\
> fi
> WARNING: Couldn't find the global config file.
> Test Run By root on Thu Aug 30 10:14:08 2007
> Native configuration is powerpc-unknown-linux-gnu
>
> === libstdc++ tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
> ERROR: tcl error sourcing
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp.
> ERROR: could not compile testsuite_abi.cc
> while executing
> "error "could not compile $f""
> (procedure "v3-build_support" line 57)
> invoked from within
> "v3-build_support"
> (file "/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp"
> line 22)
> invoked from within
> "source /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp"
> ("uplevel" body line 1)
> invoked from within
> "uplevel #0 source
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp"
> invoked from within
> "catch "uplevel #0 source $test_file_name""
> Running
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
> ERROR: tcl error sourcing
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp.
> ERROR: could not compile testsuite_abi.cc
> while executing
> "error "could not compile $f""
> (procedure "v3-build_support" line 57)
> invoked from within
> "v3-build_support"
> (file
> "/var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp"
> line 25)
> invoked from within
> "source
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp"
> ("uplevel" body line 1)
> invoked from within
> "uplevel #0 source
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp"
> invoked from within
> "catch "uplevel #0 source $test_file_name""
>
> === libstdc++ Summary ===
>
> make[4]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3/testsuite'
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
> true "AR_FLAGS=rc" "CC_FOR_BUILD=powerpc-unknown-linux-gnu-gcc"
> "CC_FOR_TARGET=/var/tmp/43/build-156/./gcc/xgcc -B/var/tmp/43/build-156/./gcc/
> -B/usr/powerpc-unknown-linux-gnu/bin/ -B/usr/powerpc-unknown-linux-gnu/lib/
> -isystem /usr/powerpc-unknown-linux-gnu/include -isystem
> /usr/powerpc-unknown-linux-gnu/sys-include" "CFLAGS=-O2 -g -O2 " "CXXFLAGS=-g
> -O2 -D_GNU_SOURCE" "CFLAGS_FOR_BUILD=-g -O2" "CFLAGS_FOR_TARGET=-O2 -g -O2 "
> "INSTALL=/usr/bin/ginstall -c" "INSTALL_DATA=/usr/bin/ginstall -c -m 644"
> "INSTALL_PROGRAM=/usr/bin/ginstall -c" "INSTALL_SCRIPT=/usr/bin/ginstall -c"
> "LDFLAGS=" "LIBCFLAGS=-O2 -g -O2 " "LIBCFLAGS_FOR_TARGET=-O2 -g -O2 "
> "MAKE=make" "MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000 "
> "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "RUNTESTFLAGS="
> "exec_prefix=/usr" "infodir=/usr/share/info" "libdir=/usr/lib"
> "includedir=/usr/include" "prefix=/usr"
> "tooldir=/usr/powerpc-unknown-linux-gnu"
> "gxx_include_dir=/usr/include/c++/4.3.0"
> "AR=/usr/powerpc-unknown-linux-gnu/bin/ar" "AS=/var/tmp/43/build-156/./gcc/as"
> "LD=/var/tmp/43/build-156/./gcc/collect-ld"
> "RANLIB=/usr/powerpc-unknown-linux-gnu/bin/ranlib"
> "NM=/var/tmp/43/build-156/./gcc/nm" "NM_FOR_BUILD="
> "NM_FOR_TARGET=/usr/powerpc-unknown-linux-gnu/bin/nm" "DESTDIR=" "WERROR="
> DO=all multi-do # make
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
> make[2]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libstdc++-v3'
> test -d testsuite || mkdir testsuite
> test -d testsuite/g++ || mkdir testsuite/g++
> (rootme=`${PWDCMD-pwd}`; export rootme; \
> srcdir=`cd ../../gcc-4.3.0/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
> cd testsuite/g++; \
> rm -f tmp-site.exp; \
> sed '/set tmpdir/ s|testsuite|testsuite/g++|' \
> < ../../site.exp > tmp-site.exp; \
> /bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
> EXPECT=expect ; export EXPECT ; \
> if [ -f ${rootme}/../expect/expect ] ; then \
> TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ;
> \
> export TCL_LIBRARY ; fi ; \
> GCC_EXEC_PREFIX="/usr/lib/gcc/" ; export GCC_EXEC_PREFIX ; \
> runtest --tool g++ )
> WARNING: Couldn't find the global config file.
> Test Run By root on Thu Aug 30 10:14:52 2007
> Native configuration is powerpc-unknown-linux-gnu
>
> === g++ tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using /var/tmp/43/gcc-4.3.0/gcc/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/bprob/bprob.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/charset/charset.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/compat/compat.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/compat/struct-layout-1.exp
> ...
> WARNING: Could not compile g++.dg/compat/struct-layout-1 generator
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/debug/debug.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/debug/dwarf2/dwarf2.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/dg.exp ...
> FAIL: g++.dg/conversion/simd1.C (test for warnings, line 8)
> FAIL: g++.dg/eh/simd-3.C execution test
> FAIL: g++.dg/ext/attribute-test-1.C (test for warnings, line 10)
> FAIL: g++.dg/ext/attribute-test-2.C (test for warnings, line 14)
> FAIL: g++.dg/ext/attribute-test-3.C (test for warnings, line 26)
> FAIL: g++.dg/ext/attribute-test-4.C (test for warnings, line 26)
> XPASS: g++.dg/tree-ssa/copyprop-1.C scan-tree-dump-not .* = [^>;]*;
> FAIL: g++.dg/warn/Wall-write-strings.C (test for warnings, line 5)
> FAIL: g++.dg/warn/write-strings-default.C (test for warnings, line 6)
> FAIL: g++.dg/warn/write-strings.C (test for warnings, line 6)
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/gcov/gcov.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/gomp/gomp.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/pch/pch.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/special/ecos.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/tls/tls.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/torture/dg-torture.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/tree-prof/tree-prof.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.dg/vect/vect.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/g++.old-deja/old-deja.exp ...
>
> === g++ Summary ===
>
> # of expected passes 16394
> # of unexpected failures 9
> # of unexpected successes 1
> # of expected failures 87
> # of unsupported tests 114
> /var/tmp/43/build-156/gcc/testsuite/g++/../../g++ version 4.3.0 20070830
> (experimental) (GCC)
>
> make[2]: [check-g++] Error 1 (ignored)
> make[2]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
> make check-am
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
> true DO=all multi-do # make
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
> make[2]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgfortran'
> test -d testsuite || mkdir testsuite
> test -d testsuite/gfortran || mkdir testsuite/gfortran
> (rootme=`${PWDCMD-pwd}`; export rootme; \
> srcdir=`cd ../../gcc-4.3.0/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
> cd testsuite/gfortran; \
> rm -f tmp-site.exp; \
> sed '/set tmpdir/ s|testsuite|testsuite/gfortran|' \
> < ../../site.exp > tmp-site.exp; \
> /bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
> EXPECT=expect ; export EXPECT ; \
> if [ -f ${rootme}/../expect/expect ] ; then \
> TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ;
> \
> export TCL_LIBRARY ; fi ; \
> GCC_EXEC_PREFIX="/usr/lib/gcc/" ; export GCC_EXEC_PREFIX ; \
> runtest --tool gfortran )
> WARNING: Couldn't find the global config file.
> Test Run By root on Thu Aug 30 10:56:12 2007
> Native configuration is powerpc-unknown-linux-gnu
>
> === gfortran tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using /var/tmp/43/gcc-4.3.0/gcc/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/dg.exp ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp
> ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/execute.exp
> ...
> FAIL: gfortran.dg/fmt_p_1.f90 -O0 execution test
> FAIL: gfortran.dg/fmt_p_1.f90 -O1 execution test
> FAIL: gfortran.dg/fmt_p_1.f90 -O2 execution test
> FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer execution test
> FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer -funroll-loops
> execution test
> FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops
> -finline-functions execution test
> FAIL: gfortran.dg/fmt_p_1.f90 -O3 -g execution test
> FAIL: gfortran.dg/fmt_p_1.f90 -Os execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O0 execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O1 execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O2 execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
> execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
> -funroll-loops execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
> -funroll-all-loops -finline-functions execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -g execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -Os execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O1 execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O2 execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
> execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
> -funroll-loops execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
> -funroll-all-loops -finline-functions execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -g execution test
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -Os execution test
> FAIL: gcc.c-torture/execute/mayalias-2.c compilation, -O3 -g (internal
> compiler error)
> FAIL: gcc.c-torture/execute/mayalias-3.c compilation, -O3 -g (internal
> compiler error)
> FAIL: gfortran.dg/nint_2.f90 -O0 execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -O0 execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -O1 execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -O2 execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer execution
> test
> FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer
> -funroll-loops execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer
> -funroll-all-loops -finline-functions execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -O3 -g execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -Os execution test
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp
> ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/unsorted/unsorted.exp
> ...
>
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/charset/charset.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/compat/compat.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp
> ...
> WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/cpp/cpp.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/cpp/trad/trad.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/debug/debug.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf2.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/dfp/dfp.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/dg.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/gomp/gomp.exp ...
> FAIL: gcc.dg/20051207-3.c (test for errors, line 7)
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/vect/vect.exp ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
> ...
> FAIL: gcc.dg/builtins-61.c scan-tree-dump return 0.0
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
> ...
> FAIL: gcc.dg/memcpy-1.c scan-tree-dump-times nasty_local 0
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/format/format.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/gomp/gomp.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/ipa/ipa.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/matrix/matrix.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/noncompile/noncompile.exp
> ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/pch/pch.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/special/mips-abi.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/special/special.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/tls/tls.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/torture/dg-torture.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/tree-prof/tree-prof.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/tree-ssa/tree-ssa.exp ...
>
> === gfortran Summary ===
>
> # of expected passes 20760
> # of unexpected failures 33
> # of expected failures 8
> # of unsupported tests 36
> /var/tmp/43/build-156/gcc/testsuite/gfortran/../../gfortran version 4.3.0
> 20070830 (experimental) (GCC)
>
> make[2]: [check-gfortran] Error 1 (ignored)
> make[2]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty'
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty/testsuite'
> make[3]: Nothing to be done for `check'.
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty/testsuite'
> make[2]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libiberty'
> make[2]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
> Making check in testsuite
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
> make check-DEJAGNU
> make[4]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
> Making a new site.exp file...
> srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd
> ../../../../gcc-4.3.0/libgomp/testsuite && pwd`; export srcdir; \
> EXPECT=expect; export EXPECT; \
> runtest=runtest; \
> if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
> l='libgomp'; for tool in $l; do \
> $runtest --tool $tool --srcdir $srcdir ; \
> done; \
> else echo "WARNING: could not find \`runtest'" 1>&2; :;\
> fi
> WARNING: Couldn't find the global config file.
> Test Run By root on Thu Aug 30 12:33:47 2007
> Native configuration is powerpc-unknown-linux-gnu
>
> === libgomp tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using /var/tmp/43/gcc-4.3.0/libgomp/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running /var/tmp/43/gcc-4.3.0/libgomp/testsuite/libgomp.c/c.exp ...
> Running /var/tmp/43/gcc-4.3.0/libgomp/testsuite/libgomp.c++/c++.exp ...
> XPASS: gcc.dg/tree-ssa/update-threading.c scan-tree-dump-times Invalid sum 0
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/i386/i386-costmodel-vect.exp
> ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/ppc/ppc-costmodel-vect.exp
> ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/spu/spu-costmodel-vect.exp
> ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/costmodel/x86_64/x86_64-costmodel-vect.exp
> ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vect/vect.exp ...
> Running /var/tmp/43/gcc-4.3.0/libgomp/testsuite/libgomp.fortran/fortran.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vmx/vmx.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/vxworks/vxworks.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.dg/weak/weak.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/acker1.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/arm-isr.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/bprob.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/dectest.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/dhry.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/gcov.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/i386-prefetch.exp
> ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/linkage.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/matrix1.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/mg-2.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/mg.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/options.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/sieve.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.misc-tests/sort2.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/alpha/alpha.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/arm/arm.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/arm/neon/neon.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/bfin/bfin.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/cris/cris.exp ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/cris/torture/cris-torture.exp
> ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/frv/frv.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/i386/i386.exp ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/i386/math-torture/math-torture.exp
> ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/ia64/ia64.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/m68k/m68k.exp ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/mips/inter/mips16-inter.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/mips/mips.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/powerpc/powerpc.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/s390/s390.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/sh/sh.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/sparc/sparc.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/spu/spu.exp ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/x86_64/abi/abi-x86_64.exp ...
> Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.target/xstormy16/xstormy16.exp
> ...
> Running
> /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.test-framework/test-framework.exp ...
> skipping test framework tests, CHECK_TEST_FRAMEWORK is not defined
>
> === gcc Summary ===
>
> # of expected passes 46252
> # of unexpected failures 5
> # of unexpected successes 1
> # of expected failures 171
> # of unresolved testcases 2
> # of untested testcases 35
> # of unsupported tests 366
> /var/tmp/43/build-156/gcc/xgcc version 4.3.0 20070830 (experimental) (GCC)
>
> make[2]: [check-gcc] Error 1 (ignored)
> make[2]: Leaving directory `/var/tmp/43/build-156/gcc'
>
> === libgomp Summary ===
>
> # of expected passes 1607
> make[4]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp/testsuite'
> make[3]: Entering directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
> true DO=all multi-do # make
> make[3]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
> make[2]: Leaving directory
> `/var/tmp/43/build-156/powerpc-unknown-linux-gnu/libgomp'
> make[1]: Leaving directory `/var/tmp/43/build-156'
>
>
> --
>
> michelin60 at gmail dot com changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |dberlin at gcc dot gnu dot
> | |org
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
2007-08-30 18:23 ` [Bug fortran/33252] " michelin60 at gmail dot com
2007-08-30 18:24 ` dberlin at dberlin dot org
@ 2007-08-30 18:35 ` pinskia at gmail dot com
2007-08-31 0:47 ` michelin60 at gmail dot com
` (12 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: pinskia at gmail dot com @ 2007-08-30 18:35 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from pinskia at gmail dot com 2007-08-30 18:35 -------
Subject: Re: GCC-4.3.0 Bootstrap testsuite error increase
> /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp.
> ERROR: could not compile testsuite_abi.cc
This was fixed by:
2007-08-30 Jakub Jelinek <jakub@redhat.com>
PR target/33168
* config/rs6000/rs6000.c (rs6000_elf_in_small_data_p): Return
true if any of the compare_section_name calls returned true,
rather than if any returned false.
Try again after that patch.
Thanks,
Andrew Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (2 preceding siblings ...)
2007-08-30 18:35 ` pinskia at gmail dot com
@ 2007-08-31 0:47 ` michelin60 at gmail dot com
2007-08-31 1:15 ` pinskia at gcc dot gnu dot org
` (11 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: michelin60 at gmail dot com @ 2007-08-31 0:47 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from michelin60 at gmail dot com 2007-08-31 00:47 -------
(> Subject: Re: GCC-4.3.0 Bootstrap testsuite error increase
>
> > /var/tmp/43/gcc-4.3.0/libstdc++-v3/testsuite/libstdc++-abi/abi.exp.
> > ERROR: could not compile testsuite_abi.cc
>
> This was fixed by:
> 2007-08-30 Jakub Jelinek <jakub@redhat.com>
>
> PR target/33168
> * config/rs6000/rs6000.c (rs6000_elf_in_small_data_p): Return
> true if any of the compare_section_name calls returned true,
> rather than if any returned false.
I am really confused now. I thought that PR33168 was fix by the patch from Dr.
Edelsohn.
It seems that Mr. Jelinek reversed the sense of the test.
In any case PR33168 referred to libstdc++ and not gfortran. In any case I
re-bootstrapped and got Mr Jelinek patch the results, still concerning gfortan
are as follows:
=== gfortran tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /var/tmp/43/gcc-4.3.0/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/dg.exp ...
FAIL: gfortran.dg/fmt_p_1.f90 -O0 execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O1 execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O2 execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/fmt_p_1.f90 -O3 -g execution test
FAIL: gfortran.dg/fmt_p_1.f90 -Os execution test
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp
...
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O0 execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O1 execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O2 execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O3 -g execution test
FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -Os execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O1 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O2 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -g execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -Os execution test
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/execute.exp
...
FAIL: gfortran.dg/nint_2.f90 -O0 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O0 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O1 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O2 execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer execution
test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/output_exponents_1.f90 -O3 -g execution test
FAIL: gfortran.dg/output_exponents_1.f90 -Os execution test
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/gomp/gomp.exp ...
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.dg/vect/vect.exp ...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
...
Running
/var/tmp/43/gcc-4.3.0/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
...
FAIL: gcc.c-torture/execute/mayalias-2.c compilation, -O3 -g (internal
compiler error)
FAIL: gcc.c-torture/execute/mayalias-3.c compilation, -O3 -g (internal
compiler error)
Running /var/tmp/43/gcc-4.3.0/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp
...
=== gfortran Summary ===
# of expected passes 20768
# of unexpected failures 33
# of expected failures 8
# of unsupported tests 36
Please bring this to the attention of the appropriate gfortran people. As a
chemical engineer I am distressed that the gfortran people are not allowed any
more to backport strictly fortran frontend improvements. Both gcc-4.2.x and
gcc-4.3.0 in the eyes of many observers and even GCC maintainers leave a lot to
be desired.
I would gladly go back to gcc-3.x.y were it not for the fortran-90/95 and
multiprocessing capabilities. Partial differential equations (occurring in
heat and mass transfer; phase change, etc) require newer capabilities.
By the same token it appears that the C-compiler is getting top heavy with
esoterica and is no longer suitable for embedded applications (low level
control of chemical reactors and status displays).
Thanks
Armando Michelin
--
michelin60 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at watson dot ibm dot
| |com, burnus at net-b dot de,
| |mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (3 preceding siblings ...)
2007-08-31 0:47 ` michelin60 at gmail dot com
@ 2007-08-31 1:15 ` pinskia at gcc dot gnu dot org
2007-08-31 1:44 ` michelin60 at gmail dot com
` (10 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-08-31 1:15 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from pinskia at gcc dot gnu dot org 2007-08-31 01:15 -------
First off don't CC anyone unless there is a real reason to like you know they
caused the issue. Second most of the rest of the failures are PR 33225
anyways.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|dje at watson dot ibm dot |
|com, dberlin at gcc dot gnu |
|dot org, mark at |
|codesourcery dot com |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (4 preceding siblings ...)
2007-08-31 1:15 ` pinskia at gcc dot gnu dot org
@ 2007-08-31 1:44 ` michelin60 at gmail dot com
2007-08-31 1:51 ` Andrew Pinski
2007-08-31 1:51 ` pinskia at gcc dot gnu dot org
` (9 subsequent siblings)
15 siblings, 1 reply; 20+ messages in thread
From: michelin60 at gmail dot com @ 2007-08-31 1:44 UTC (permalink / raw)
To: gcc-bugs
------- Comment #6 from michelin60 at gmail dot com 2007-08-31 01:43 -------
(In reply to comment #5)
> First off don't CC anyone unless there is a real reason to like you know they
> caused the issue. Second most of the rest of the failures are PR 33225
> anyways.
>
First of all I CC'd Dr. Edelsohn because I mentioned him and he was the acting
on PR33168, you chimed in about 24 hours later. Even you mention somebody
involved by name it is common curtesy to make that person aware of that
mention.
Second I mentioned Mark Mitchell because he, as relesae manager, put a stop to
backporting
definitely aggravating productive use of GCC.
Third you mentioning PR33168 out of context instead of PR33225 was just plain
dumb so I CC'd Burnus because he seems to be working pretty hard to make
gfortran usable.
Last but not least, there are even two ICE's (mayalias) in the test results
that I did not feel making an issue of.
Result, do not force me to contact these people directly when you do not take
the pain of even reading submissions.
--
michelin60 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at watson dot ibm dot
| |com, mark at codesourcery
| |dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-31 1:44 ` michelin60 at gmail dot com
@ 2007-08-31 1:51 ` Andrew Pinski
0 siblings, 0 replies; 20+ messages in thread
From: Andrew Pinski @ 2007-08-31 1:51 UTC (permalink / raw)
To: gcc-bugzilla; +Cc: gcc-bugs
On 31 Aug 2007 01:43:51 -0000, michelin60 at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
> Second I mentioned Mark Mitchell because he, as relesae manager, put a stop to
> backporting
> definitely aggravating productive use of GCC.
This is the trunk we are talking about, I am seriously thinking you
need to understand what that means. There is no backporting, it is
all going into the trunk and you are using the trunk so you get what
everyone else gets sometimes, a broken compiler. THis is normal for
any kind of development.
> Third you mentioning PR33168 out of context instead of PR33225 was just plain
> dumb so I CC'd Burnus because he seems to be working pretty hard to make
> gfortran usable.
It was just fixed so update and try again.
>
> Last but not least, there are even two ICE's (mayalias) in the test results
> that I did not feel making an issue of.
Yes we know about those, if did a quick search, you would find that I
filed the bug about those before I added those testcase.
>
> Result, do not force me to contact these people directly when you do not take
> the pain of even reading submissions.
And again, this is the trunk we are talking about, not some release
branch and we are not even in stage 3 yet so there will be issues.
-- Pinski
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (5 preceding siblings ...)
2007-08-31 1:44 ` michelin60 at gmail dot com
@ 2007-08-31 1:51 ` pinskia at gcc dot gnu dot org
2007-08-31 2:39 ` jvdelisle at gcc dot gnu dot org
` (8 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-08-31 1:51 UTC (permalink / raw)
To: gcc-bugs
------- Comment #7 from pinskia at gcc dot gnu dot org 2007-08-31 01:51 -------
Subject: Re: GCC-4.3.0 Bootstrap testsuite error increase
On 31 Aug 2007 01:43:51 -0000, michelin60 at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
> Second I mentioned Mark Mitchell because he, as relesae manager, put a stop to
> backporting
> definitely aggravating productive use of GCC.
This is the trunk we are talking about, I am seriously thinking you
need to understand what that means. There is no backporting, it is
all going into the trunk and you are using the trunk so you get what
everyone else gets sometimes, a broken compiler. THis is normal for
any kind of development.
> Third you mentioning PR33168 out of context instead of PR33225 was just plain
> dumb so I CC'd Burnus because he seems to be working pretty hard to make
> gfortran usable.
It was just fixed so update and try again.
>
> Last but not least, there are even two ICE's (mayalias) in the test results
> that I did not feel making an issue of.
Yes we know about those, if did a quick search, you would find that I
filed the bug about those before I added those testcase.
>
> Result, do not force me to contact these people directly when you do not take
> the pain of even reading submissions.
And again, this is the trunk we are talking about, not some release
branch and we are not even in stage 3 yet so there will be issues.
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (6 preceding siblings ...)
2007-08-31 1:51 ` pinskia at gcc dot gnu dot org
@ 2007-08-31 2:39 ` jvdelisle at gcc dot gnu dot org
2007-08-31 2:43 ` kargl at gcc dot gnu dot org
` (7 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: jvdelisle at gcc dot gnu dot org @ 2007-08-31 2:39 UTC (permalink / raw)
To: gcc-bugs
------- Comment #8 from jvdelisle at gcc dot gnu dot org 2007-08-31 02:39 -------
As Andrew stated, most of these testsuite failures were due to a regression
caused by one of my patches. I do monitor bugzilla submissions during the day.
However, I do this work in the evenings as a volunteer. Since I live on the
west side of the US, there is usually a several hour delay before I can get
around to responding, if I have time. I think people will agree that I do read
these submissions when they are related to my areas of interest.
That patch has been reverted. PR33225.
--
jvdelisle at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|mark at codesourcery dot com|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (7 preceding siblings ...)
2007-08-31 2:39 ` jvdelisle at gcc dot gnu dot org
@ 2007-08-31 2:43 ` kargl at gcc dot gnu dot org
2007-08-31 4:33 ` michelin60 at gmail dot com
` (6 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: kargl at gcc dot gnu dot org @ 2007-08-31 2:43 UTC (permalink / raw)
To: gcc-bugs
------- Comment #9 from kargl at gcc dot gnu dot org 2007-08-31 02:43 -------
> Second I mentioned Mark Mitchell because he, as relesae manager, put a stop
> to backporting definitely aggravating productive use of GCC.
I'm disinterested in the rest of this PR, but I will comment on the above.
gfortran through the 4.1.x and 4.2.0 releases started to abuse the leniency
it was granted with respect to deviating from the normal release branch rules.
With 3 active branch I communicated with other gfortran deverlopers about
following the release branch rules because it was simply too difficult to
manage and backport with our current manpower. I then asked Mark for his
opinion, and he was more than happy to have gfortran fall in-line with the
other front ends.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (8 preceding siblings ...)
2007-08-31 2:43 ` kargl at gcc dot gnu dot org
@ 2007-08-31 4:33 ` michelin60 at gmail dot com
2007-08-31 7:59 ` Andrew Pinski
2007-08-31 5:29 ` kargl at gcc dot gnu dot org
` (5 subsequent siblings)
15 siblings, 1 reply; 20+ messages in thread
From: michelin60 at gmail dot com @ 2007-08-31 4:33 UTC (permalink / raw)
To: gcc-bugs
------- Comment #10 from michelin60 at gmail dot com 2007-08-31 04:33 -------
(In reply to comment #7)
> Subject: Re: GCC-4.3.0 Bootstrap testsuite error increase
>
> > Second I mentioned Mark Mitchell because he, as relesae manager, put a stop to backporting definitely aggravating productive use of GCC.
> This is the trunk we are talking about, I am seriously thinking you
> need to understand what that means. There is no backporting, it is
> And again, this is the trunk we are talking about, not some release
> branch and we are not even in stage 3 yet so there will be issues.
> It was just fixed so update and try again.
>
> Yes we know about those, if did a quick search, you would find that I
> filed the bug about those before I added those testcase.
Regarding the last quote I am led to believe that Mr. Pinski is taking undue
credit. PR30758 (marked as a duplicate) is the first addressing the
re-appearance of mayalias. there are another 5 PR, all appearing before Mr.
Pinski's filing.
This reminds me of what happened regarding PR33125 (filed by myself) and
PR33126. Neither made to the bug list; neither has been officially closed.
Anyhow the patch submitted seems to have resolved the issue.
I updated, and I am now bootstrapping with check. I am sure Mr Delisle patch
originally worked and passed tests; but, that some other later patch gave rise
to what I, and seemingly others, saw in PR33252. I took issue with Mr. Pinski's
confusing PR32225 with PR33125 not Mr Delisle volunteer work.
Now to the more confusing issue of backporting. I managed to find the
following:
> IMO, for the Fortran front end, "regressions-only" is an inappropriate
> criterion for this sort of mode, given that the front end does not have
> a long history for the wrong-code and ICE-on-valid bugs to be
> regressions against.
I think that's less true than it used to be. It's true that gfortran is
new-ish, and I've given the Fortran team a lot of flexibility in past
release cycles. But, congratulations are in order: gfortran is now a
real Fortran compiler and people really are using it! But,
"regressions, wrong-code, and ICEs" isn't a bad criteria for this
intermediate lockdown.
I do expect Fortran to honor the regressions-only rule once the 4.3
release branch has been made.
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
Mr Kargl explains what happened from an maintainer's and release manager's view
but does not provide a paliative to the user. G77 relative to g90 is relatively
much more out of date than C1989 to C1994. Anyhow, if memory serves, there was
significant back-porting from 4.3 to 4.2.x to to solve some memory usage
problems.
Michelin
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-31 4:33 ` michelin60 at gmail dot com
@ 2007-08-31 7:59 ` Andrew Pinski
0 siblings, 0 replies; 20+ messages in thread
From: Andrew Pinski @ 2007-08-31 7:59 UTC (permalink / raw)
To: gcc-bugzilla; +Cc: gcc-bugs
On 31 Aug 2007 04:33:12 -0000, michelin60 at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
> Regarding the last quote I am led to believe that Mr. Pinski is taking undue
> credit. PR30758 (marked as a duplicate) is the first addressing the
> re-appearance of mayalias. there are another 5 PR, all appearing before Mr.
> Pinski's filing.
Wait one minute, did you read PR 28834 (note how the number is lower)?
Also read comment #1:
>Note this is the testcase for
> 28807 which I was using for testing so the testcase might be added to the
> testsuite by the time someone gets around to looking into the bug.
Also you know what the testcase for PR 28807 is named?
(gcc.c-torture/execute/mayalias-2.c). The other testcase was added by
me for PR 28812. Notice a pattern here?
So how can my PR not be for the the mayalias testcase failure when I
filed the bug specifically so I did not get blamed for a testcase
failure :). There is no re-appearance of the mayalias failure; just
for 4.2, the testcase was marked as xfail. Nothing changed inbetween
I filed the bug report and the other one was filed except for the
tetcase being xfailed on the 4.2 branch. I think you need to go read
more of the history behind this one. Since I know all about this
testcase failure as I added the testcases :). If you don't want to
give me credit that is not my fault but oh well.
I am getting tried of being wrongly accused for stuff I do correctly
by unknowns.
And again this is the trunk we are talking about so how can Mark be
involved for every day breakage? Also if you are using the trunk you
have to understand there will be breakage and take it and report it
without being all offensive about problems like this.
-- Pinski
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (9 preceding siblings ...)
2007-08-31 4:33 ` michelin60 at gmail dot com
@ 2007-08-31 5:29 ` kargl at gcc dot gnu dot org
2007-08-31 8:00 ` pinskia at gcc dot gnu dot org
` (4 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: kargl at gcc dot gnu dot org @ 2007-08-31 5:29 UTC (permalink / raw)
To: gcc-bugs
------- Comment #11 from kargl at gcc dot gnu dot org 2007-08-31 05:29 -------
(In reply to comment #10)
> Now to the more confusing issue of backporting. I managed to find the
> following:
>
(Stuff from Mark removed)
You're quoting email out of context.
>
> Mr Kargl explains what happened from an maintainer's and release manager's
> view but does not provide a paliative to the user. G77 relative to g90 is
> relatively much more out of date than C1989 to C1994.
I can't parse the above.
> Anyhow, if memory serves, there was significant back-porting from 4.3
> to 4.2.x to to solve some memory usage problems.
Yes, there was backporting to 4.2.0. This backporting was reduced
within the 4.2.1 time frame. It almost completely ceased several
months ago. The 4.2 branch and trunk had diverged too much.
Dude, just give it a rest. Trunk gets broken sometimes. I broke it
for some targets when I integrated the ISO C binding feature in a much
worse way. One could not even bootstrap GCC. I spent a very nerve
wracking 3 days trying to fix it.
PS: It's the attitude (that I preceive) expressed by you in this PR
(and other recent users) that has driven my decision to stop working
on gfortran.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (10 preceding siblings ...)
2007-08-31 5:29 ` kargl at gcc dot gnu dot org
@ 2007-08-31 8:00 ` pinskia at gcc dot gnu dot org
2007-08-31 11:10 ` fxcoudert at gcc dot gnu dot org
` (3 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-08-31 8:00 UTC (permalink / raw)
To: gcc-bugs
------- Comment #12 from pinskia at gcc dot gnu dot org 2007-08-31 07:59 -------
Subject: Re: GCC-4.3.0 Bootstrap testsuite error increase
On 31 Aug 2007 04:33:12 -0000, michelin60 at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
> Regarding the last quote I am led to believe that Mr. Pinski is taking undue
> credit. PR30758 (marked as a duplicate) is the first addressing the
> re-appearance of mayalias. there are another 5 PR, all appearing before Mr.
> Pinski's filing.
Wait one minute, did you read PR 28834 (note how the number is lower)?
Also read comment #1:
>Note this is the testcase for
> 28807 which I was using for testing so the testcase might be added to the
> testsuite by the time someone gets around to looking into the bug.
Also you know what the testcase for PR 28807 is named?
(gcc.c-torture/execute/mayalias-2.c). The other testcase was added by
me for PR 28812. Notice a pattern here?
So how can my PR not be for the the mayalias testcase failure when I
filed the bug specifically so I did not get blamed for a testcase
failure :). There is no re-appearance of the mayalias failure; just
for 4.2, the testcase was marked as xfail. Nothing changed inbetween
I filed the bug report and the other one was filed except for the
tetcase being xfailed on the 4.2 branch. I think you need to go read
more of the history behind this one. Since I know all about this
testcase failure as I added the testcases :). If you don't want to
give me credit that is not my fault but oh well.
I am getting tried of being wrongly accused for stuff I do correctly
by unknowns.
And again this is the trunk we are talking about so how can Mark be
involved for every day breakage? Also if you are using the trunk you
have to understand there will be breakage and take it and report it
without being all offensive about problems like this.
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (11 preceding siblings ...)
2007-08-31 8:00 ` pinskia at gcc dot gnu dot org
@ 2007-08-31 11:10 ` fxcoudert at gcc dot gnu dot org
2007-08-31 14:52 ` michelin60 at gmail dot com
` (2 subsequent siblings)
15 siblings, 0 replies; 20+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2007-08-31 11:10 UTC (permalink / raw)
To: gcc-bugs
------- Comment #13 from fxcoudert at gcc dot gnu dot org 2007-08-31 11:10 -------
Allow me to step in... michelin60, what about discussing constructively? Here
are the comments I can make one the failures and your remarks. Please answer to
them, or ask further questions if something isn't clear.
> FAIL: gfortran.dg/fmt_p_1.f90 -O0 execution test
> FAIL: gfortran.dg/large_real_kind_form_io_1.f90 -O0 execution test
> FAIL: gfortran.dg/output_exponents_1.f90 -O0 execution test
As explained earlier, these failures are due to a patch that was reverted in
less than 48 hours. This is a good example of why large testing of development
branches is important, as well as a good example of why you shouldn't use a
development branch for production.
> FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test
This one has been failing for quite some time. It concerns the output of very
large real(kind=16) numbers, which are output as infinities. What is missing
for Jerry or I to develop a patch is access to such a machine (ppc-darwin,
ppc-linux or a recent sparc-solaris are good candidates). This is considered a
corner case, and thus of lower importance.
> FAIL: gfortran.dg/nint_2.f90 -O0 execution test
This one is annoying, I think I had it fixed (I saw it on numerous targets, and
fixed it on most... I believed it was fixed on all targets). If you are willing
to get this fixed, please open a PR specifically for this problem, adding the
relevant output from ${builddir}/gcc/testsuite/gfortran/gfortran.log.
Additionally, you might want to compile and run the testcase outside of the
testsuite framework, see what happens and put that into the bugreport.
Hopefully, I can work on fixing that with you (asking you to perform any
further inquiries).
> Please bring this to the attention of the appropriate gfortran people. As a
> chemical engineer I am distressed that the gfortran people are not allowed any
> more to backport strictly fortran frontend improvements. Both gcc-4.2.x and
> gcc-4.3.0 in the eyes of many observers and even GCC maintainers leave a lot
> to be desired.
"backporting" means "porting changes, originaly designed for the development
branch [here 4.3], to release branches [branches for which at least one version
was released, like 4.2 and 4.1]". The exact rule in place for GCC development
is that only patches fixing regressions can be backported to release branches
(a regression is a bug that wasn't present in older versions but appeared at
some point). This prevents (among other things) new features to be introduced
in old branches. This is done to keep release branch stables, to avoid
introducing regressions inside a branch. The golden rule here is: all user code
that compiled fine with version 4.2.x should compile fine with later versions
4.2.y (y > x). A user should never face negative consequences for upgrading his
compiler inside a given branch.
Now, the backport limitation cannot hurt 4.3, because it is the development
branch. We can (and do) perform any change that we deem necessary to the
development branch, either to introduce new features, to fix bugs (be them
regressions or not).
Now, any judgment on the intrinsic quality of a compiler is very difficult to
make. If there are specific problems you encounter with gfortran, I see
basically 3 ways you can get it improving:
* reporting your specific problems (one PR per bug/misbehaviour encountered)
* contributing time to the project (reporting bugs is one of them, regularly
testing GCC on differents platforms you have access to is another, as is
helping Fortran newbies on the mailing-list; this gives more time to the
maintainers to actually maintain the compiler itself)
* contributing resources to the project (e.g. access to specific hardware)
Short of that, well, you still have the option of using/buying another
compiler.
PS: most developers of gfortran are also end-users of the compiler, and
volunteers. Most of us are academic or private researchers. Writing this long
explanation took 30 minutes of my working day, and thus impacted my own
resarch, so please consider it seriously. (I also am a working in physical
chemistry, have a few friends working with Michelin.)
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu dot
| |org
GCC build triplet|powerpc |powerpc-unknown-linux-gnu
GCC host triplet|powerpc |powerpc-unknown-linux-gnu
GCC target triplet|powerpc |powerpc-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (12 preceding siblings ...)
2007-08-31 11:10 ` fxcoudert at gcc dot gnu dot org
@ 2007-08-31 14:52 ` michelin60 at gmail dot com
2007-08-31 15:52 ` michelin60 at gmail dot com
2007-09-03 10:44 ` fxcoudert at gcc dot gnu dot org
15 siblings, 0 replies; 20+ messages in thread
From: michelin60 at gmail dot com @ 2007-08-31 14:52 UTC (permalink / raw)
To: gcc-bugs
------- Comment #14 from michelin60 at gmail dot com 2007-08-31 14:52 -------
>
> > FAIL: gfortran.dg/nint_2.f90 -O0 execution test
>
This one is annoying, I think I had it fixed (I saw it on numerous targets, and
fixed it on most... I believed it was fixed on all targets). If you are willing
> to get this fixed, please open a PR specifically for this problem, adding the
> relevant output from ${builddir}/gcc/testsuite/gfortran/gfortran.log.
> Additionally, you might want to compile and run the testcase outside of the
> testsuite framework, see what happens and put that into the bugreport.
> Hopefully, I can work on fixing that with you (asking you to perform any
> further inquiries).
>
> PS: most developers of gfortran are also end-users of the compiler, and
> volunteers. Most of us are academic or private researchers. Writing this long
> explanation took 30 minutes of my working day, and thus impacted my own
> resarch, so please consider it seriously. (I also am a working in physical
> chemistry, have a few friends working with Michelin.)
>
Thank you for your detailed and informative response. Glad to work with sombody
in the physical sciences. I was/am not smart enough to get into physical
chemistry. My family background is Northern Italy and any connection to the
French branch must have occurred centuries ago.
Let us start with the easiest one for me as this is the last working day of my
vacation, I cannot give access to to my dual G4 machine as my Internet
connection does not allow outside initiated connection. I will immediately
gather data on nint_2.f90 and open an PR.
Thanks again
Armando
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (13 preceding siblings ...)
2007-08-31 14:52 ` michelin60 at gmail dot com
@ 2007-08-31 15:52 ` michelin60 at gmail dot com
2007-09-03 10:44 ` fxcoudert at gcc dot gnu dot org
15 siblings, 0 replies; 20+ messages in thread
From: michelin60 at gmail dot com @ 2007-08-31 15:52 UTC (permalink / raw)
To: gcc-bugs
------- Comment #15 from michelin60 at gmail dot com 2007-08-31 15:52 -------
> > Regarding the last quote I am led to believe that Mr. Pinski is taking undue
> > credit. PR30758 (marked as a duplicate) is the first addressing the
> > re-appearance of mayalias. there are another 5 PR, all appearing before Mr.
> > Pinski's filing.
>
> Wait one minute, did you read PR 28834 (note how the number is lower)?
> Also read comment #1:
> >Note this is the testcase for
> > 28807 which I was using for testing so the testcase might be added to the
> > testsuite by the time someone gets around to looking into the bug.
>
What confused me (and I take full blame for it) was the following:
------- Comment #7 From Andrew Pinski 2006-08-24 15:16 [reply] -------
Mine, all mine.
------- Comment #8 From patchapp@dberlin.org 2006-08-24 15:18 [reply] -------
Subject: Bug number PR 28807
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2006-08/msg00878.html
------- Comment #9 From Andrew Pinski 2006-08-25 07:14 [reply] -------
Fixed.
Any further discussion with Mr Pinski and Mr. Kargl seems pointless as thanks
to Mr. Coudert I am engaged in doing something constructive.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread* [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
2007-08-30 18:10 [Bug fortran/33252] New: GCC-4.3.0 Bootstrap testsuite error increase michelin60 at gmail dot com
` (14 preceding siblings ...)
2007-08-31 15:52 ` michelin60 at gmail dot com
@ 2007-09-03 10:44 ` fxcoudert at gcc dot gnu dot org
15 siblings, 0 replies; 20+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2007-09-03 10:44 UTC (permalink / raw)
To: gcc-bugs
------- Comment #16 from fxcoudert at gcc dot gnu dot org 2007-09-03 10:44 -------
The Fortran part has its PR, I saw a PR for some C problem also, so I'm closing
this. If other you experience other powerpc regressions, please open new PRs.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252
^ permalink raw reply [flat|nested] 20+ messages in thread