Dennis Clarke <dcla...@blastwave.org> writes: > Q: is there a way to prevent a test timing out ? > > I see a lot of this sort of thing : > > Running /opt/bw/src/gcc-4.5.3/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. > . > . > . > > Somewhat annoying as I am in no particular hurry. :-)
You could get a faster computer. Or you can edit gcc/site.exp in your build directory to set tool_timeout to a large value. The number is in seconds, and the default is 300. Ian
