This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
GCC 4.5.2 Release Candidate : WARNING: program timed out.
- From: Dennis Clarke <dclarke at blastwave dot org>
- To: gcc at gcc dot gnu dot org
- Date: Sat, 11 Dec 2010 23:34:02 -0500 (EST)
- Subject: GCC 4.5.2 Release Candidate : WARNING: program timed out.
- Reply-to: dclarke at blastwave dot org
While running the testsuite I see a number of warnings related to
timeouts. Is there some way to avoid these annoyances?
Thus :
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description
file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file
for target.
Using
/export/medusa/dclarke/build/GCC/4.5.2-RC/RC-20101208/gcc/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/export/medusa/dclarke/build/GCC/4.5.2-RC/RC-20101208/gcc/testsuite/gcc.c-torture/compile/compile.exp
...
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -O0 (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -O1 (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -O2 (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -O3 -fomit-frame-pointer (test for
excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -O3 -g (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -Os (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -O2 -flto (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr46534.c -O2 -fwhopr (test for excess errors)
.
.
.
--
Dennis Clarke
dclarke@opensolaris.ca <- Email related to the open source Solaris
dclarke@blastwave.org <- Email related to open source for Solaris