This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/48283] gcc.dg/graphite/block-[3478].c timeouts
- From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 25 Mar 2011 12:35:05 +0000
- Subject: [Bug testsuite/48283] gcc.dg/graphite/block-[3478].c timeouts
- Auto-submitted: auto-generated
- References: <bug-48283-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48283
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-03-25 12:35:03 UTC ---
> --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-25 12:26:55 UTC ---
> Just to clarify - runtime or compile-time issue? I see the testcases
> operate on 100^3 arrays - certainly not small for very slow HW.
Compile time, runtime for block-3.exe is 0.06 s even on the R10k
machine.
> I'd say skip graphite tests completely for !run_expensive_tests for now.
I'd rather tag the four culprits only for the moment to keep some
coverage.
Rainer