This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/53852] [4.8 Regression] -ftree-loop-linear: large compile time / memory usage
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 19 Feb 2013 20:47:03 +0000
- Subject: [Bug tree-optimization/53852] [4.8 Regression] -ftree-loop-linear: large compile time / memory usage
- Auto-submitted: auto-generated
- References: <bug-53852-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53852
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P2
CC| |law at redhat dot com
--- Comment #8 from Jeffrey A. Law <law at redhat dot com> 2013-02-19 20:47:03 UTC ---
I'm downgrading this to a P2. Graphite is an optional component and with
somewhat dubious value. While I hate to see compile-time and memory
consumption problems of this nature, I can't support this PR as being important
enough to be a release blocker.
I took a look to see if there was some reasonable way to throttle the
compile-time and memory consumption, but from what I can tell (with minimal
graphite/ISL knowledge), the sizes of the maps we're passing down to the ISL
code aren't terribly big. Yet something in the ISL code just goes bananas.