I'm building the brand new gcc-4.3.3 and I see massive failures during 'make-k
test':
FAIL: libmudflap.c++/pass41-frag.cxx execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-static) execution test
FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test
Running
/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libmudflap/testsuite/libmudflap.c++/ctors.exp
...
Running
/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libmudflap/testsuite/libmudflap.cth/cthfrags.exp
...
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c execution test
FAIL: libmudflap.cth/pass37-frag.c output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 1) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 1) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 4) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 4) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 5) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 5) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 6) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 6) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 7) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 7) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 8) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 8) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 9) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 9) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 10) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 10) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 13) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 13) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 17) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 17) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 18) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 18) output pattern test
WARNING: program timed out.
FAIL: libmudflap.cth/pass37-frag.c (rerun 19) execution test
FAIL: libmudflap.cth/pass37-frag.c (rerun 19) output pattern test
WARNING: program timed out.
...
.
I know that test suite failures are not considered to be bugs, but the point is
that I had no such failures while building gcc-4.3.2 exactly the same way with
the same dependencies, so _maybe_ it's a regression failure.
--
Summary: massive failures during 'make -k test' in 'libmudflap'
Product: gcc
Version: 4.3.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: sergstesh at yahoo dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38963
