Re: More testsuite info

> Rebuilding ubuntu gcc-4.2 with the ubuntu glibc-2.5 that was build
> with ubuntu gcc-4.2, I have three fewer failures in the gcc testsuite:
> 
> FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -fomit-frame-pointer  (test for ex
> cess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -g  (test for excess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/20001226-1.c  -Os  (test for excess errors)

This is a known issue and a GCC PR.  Essentially, GCC has gotten
slower over the years and this test fails on slow machines.  One
factor is the checking that's done prior to release.  You can disable
this with the configure option "--disable-checking".

> two fewer failures in libmudflap:
> FAIL: libmudflap.cth/pass39-frag.c (-O2) (rerun 16) execution test
> FAIL: libmudflap.cth/pass39-frag.c (-O2) (rerun 16) output pattern test

These were probably timeouts.  I don't see any libmudflap fails with
gcc-4.2 and linuxthreads.  If you have failures that aren't timeouts,
they need investigation.

> one fewer failure in libstdc++:
> FAIL: thread/pthread5.cc execution test
> 
> but four additional ones:
> WARNING: program timed out.
> FAIL: thread/pthread1.cc execution test
> WARNING: program timed out.
> FAIL: thread/pthread3.cc execution test
> WARNING: program timed out.
> FAIL: tr1/2_general_utilities/memory/shared_ptr/thread/default_weaktoshared.cc e
> xecution test
> FAIL: tr1/2_general_utilities/memory/shared_ptr/thread/mutex_weaktoshared.cc exe
> cution test

These don't fail with linuxthreads.  If mutex_weaktoshared didn't timeout,
then there's an implementation problem with threads (e.g., bug reported
by Aurelien).

Dave
-- 
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)