http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48283
Summary: gcc.dg/graphite/block-[3478].c timeouts
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: r...@gcc.gnu.org
CC: s...@gcc.gnu.org
Host: sparc-sun-solaris2.*, mips-sgi-irix6.5
Target: sparc-sun-solaris2.*, mips-sgi-irix6.5
Build: sparc-sun-solaris2.*, mips-sgi-irix6.5
The for graphite testcases gcc.dg/graphite/block-[3478].c regularly time out on
Solaris/SPARC and IRIX hosts despite already using dg-timeout-factor 4, i.e.
they
take longer than 20 minutes (40 minutes on IRIX where I've doubled the default
to account for the slower CPUs) to complete.
Here are the compile times on onloaded machines:
* i386-pc-solaris2.11, 1.6 GHz Core i7:
real 2:19.73
user 2:16.56
sys 0.10
* sparc-sun-solaris2.10, 1.35 GHz UltraSPARC IV+:
real 5:52.77
user 5:52.22
sys 0.14
* sparc-sun-solaris2.11, 1.2 GHz UltraSPARC-T2:
real 16:23.64
user 16:21.71
sys 0.49
* mips-sgi-irix6.5, 250 MHz MIPS R10000:
real 41:34.05
user 41:21.31
sys 0.78
Both systems are multilibbed, so 4 tests timing out add 160 minutes to the
test time, which I consider way over the top. In light of the policy in
http://gcc.gnu.org/ml/gcc-patches/2011-02/msg00059.html
either consider reducing the runtime of the test to be within the limits
outlined there or flag it as expensive using dg-require-effective-target
run_expensive_tests.
