> Dennis Clarke wrote:
>> Is there a way to allow the testsuite to just run regardless of howlong it
>> takes?
>>
>> I am getting "program timed out" warnings for multiple tests :
>>
>> Running
>> /export/home/dclarke/build/gcc-4.2.1/gcc/testsuite/gcc.c-torture/compile/compile.exp
>> ...
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c -O1 (test for excess errors)
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c -O2 (test for excess errors)
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c -O3 -fomit-frame-pointer (test
>> for excess errors)
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c -O3 -g (test for excess errors)
>> WARNING: program timed out.
>>
>>
> You need a faster computer.
Trust me .. I know. :-)
I do have access to top of the line Sun gear but I am running this
experiment and this bootstrap on this machine.
Thus, the question stands :
Is there a way to allow the testsuite to just run regardless of
how long it takes?
Dennis
