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: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 25 Mar 2011 12:27: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
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |compile-time-hog
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.03.25 12:26:55
Ever Confirmed|0 |1
--- 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 seems to be excessively high for x86_64 machines as well,
Sebastian, why is graphite soooo slow on these very small testcases?
Execution is quick for me. All time is spent in
samples % app name symbol name
1281556 58.0817 libppl.so.9.0.0 /usr/lib64/libppl.so.9.0.0
466710 21.1519 libc-2.9.so /lib64/libc-2.9.so
250459 11.3511 libgmp.so.3.5.0 /usr/lib64/libgmp.so.3.5.0
(note this is a whole-system profile).
I'd say skip graphite tests completely for !run_expensive_tests for now.