[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 Richard Guenther changed: What|Removed |Added Target Milestone|4.4.6 |4.5.0
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 Sebastian Pop changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #13 from Sebastian Pop 2011-02-02 18:44:29 UTC --- Alright, then let's mark this as fixed.
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 --- Comment #12 from Diego Novillo 2011-02-02 18:15:18 UTC --- Author: dnovillo Date: Wed Feb 2 18:15:10 2011 New Revision: 169744 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169744 Log: 2011-02-01 Richard Guenther PR tree-optimization/47555 Revert 2010-07-15 Sebastian Pop * params.def (PARAM_SCEV_MAX_EXPR_SIZE): Bump the value to 100. * gcc.dg/pr47555.c: New testcase. Added: branches/google/integration/gcc/testsuite/gcc.dg/pr47555.c Modified: branches/google/integration/gcc/ChangeLog branches/google/integration/gcc/params.def branches/google/integration/gcc/testsuite/ChangeLog
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 --- Comment #11 from rguenther at suse dot de 2011-02-02 16:29:46 UTC --- On Wed, 2 Feb 2011, spop at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 > > --- Comment #10 from Sebastian Pop 2011-02-02 > 16:01:34 UTC --- > What about backporting this patch to 4.4 and 4.5? I don't think this is a good idea. Richard.
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 --- Comment #10 from Sebastian Pop 2011-02-02 16:01:34 UTC --- What about backporting this patch to 4.4 and 4.5?
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 --- Comment #9 from Sebastian Pop 2011-02-02 15:52:15 UTC --- Author: spop Date: Wed Feb 2 15:52:08 2011 New Revision: 169530 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169530 Log: Fix PR47576 and PR47555: add PARAM_SCEV_MAX_EXPR_COMPLEXITY. 2011-02-02 Sebastian Pop PR tree-optimization/47576 PR tree-optimization/47555 * doc/invoke.texi (scev-max-expr-complexity): Documented. * params.def (PARAM_SCEV_MAX_EXPR_SIZE): Bump the value to 100. (PARAM_SCEV_MAX_EXPR_COMPLEXITY): Declared. * tree-scalar-evolution.c (follow_ssa_edge): Use PARAM_SCEV_MAX_EXPR_COMPLEXITY. Modified: trunk/gcc/ChangeLog trunk/gcc/doc/invoke.texi trunk/gcc/params.def trunk/gcc/tree-scalar-evolution.c
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 Sebastian Pop changed: What|Removed |Added Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |spop at gcc dot gnu.org |gnu.org | --- Comment #8 from Sebastian Pop 2011-02-01 19:56:46 UTC --- Patch here: http://gcc.gnu.org/ml/gcc-patches/2011-02/msg00064.html
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 --- Comment #7 from rguenther at suse dot de 2011-02-01 14:48:15 UTC --- On Tue, 1 Feb 2011, tony.poppleton at gmail dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 > > --- Comment #6 from Tony Poppleton > 2011-02-01 14:45:28 UTC --- > Out of interest, could this parameter of 20 be automatically tuned based on > the > available RAM? > > For systems with a lot of RAM, it might make sense to increase the parameter > above 20 (assuming this produces better code in the end). > > Whilst they could override this using the flag mentioned in comment #3, > auto-detecting this parameter would make it easier for the end user. We try very hard to not have generated code depend on host machine configuration. So, no.
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 --- Comment #6 from Tony Poppleton 2011-02-01 14:45:28 UTC --- Out of interest, could this parameter of 20 be automatically tuned based on the available RAM? For systems with a lot of RAM, it might make sense to increase the parameter above 20 (assuming this produces better code in the end). Whilst they could override this using the flag mentioned in comment #3, auto-detecting this parameter would make it easier for the end user.
[Bug tree-optimization/47555] [4.4 Regression] Huge memory usage when optimizing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47555 Richard Guenther changed: What|Removed |Added Known to work||4.6.0 Summary|[4.4/4.6 Regression] Huge |[4.4 Regression] Huge |memory usage when |memory usage when |optimizing |optimizing Known to fail|4.6.0 | --- Comment #5 from Richard Guenther 2011-02-01 14:36:41 UTC --- Re-fixed on trunk. Eventually this is now a dup of an existing bug.
