public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/28463] New: Using -fdump-tree-optimized causes a huge compile time memory regression
@ 2006-07-23 15:14 rguenth at gcc dot gnu dot org
2006-07-23 15:22 ` [Bug middle-end/28463] [4.0/4.1/4.2 Regression] " steven at gcc dot gnu dot org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: rguenth at gcc dot gnu dot org @ 2006-07-23 15:14 UTC (permalink / raw)
To: gcc-bugs
Enabling some tree dumps causes a tramp3d-v4 compile to run into swap,
requiring
about 50% more ram than a non-dumped compile.
Pinskia suggests
Index: gcc/cgraph.c
===================================================================
--- gcc/cgraph.c (revision 115684)
+++ gcc/cgraph.c (working copy)
@@ -509,7 +509,7 @@ cgraph_remove_node (struct cgraph_node *
kill_body = true;
}
- if (kill_body && !dump_enabled_p (TDI_tree_all) && flag_unit_at_a_time)
+ if (kill_body && flag_unit_at_a_time)
{
DECL_SAVED_TREE (node->decl) = NULL;
DECL_STRUCT_FUNCTION (node->decl) = NULL;
Index: gcc/cgraphunit.c
===================================================================
--- gcc/cgraphunit.c (revision 115684)
+++ gcc/cgraphunit.c (working copy)
@@ -1466,7 +1466,6 @@ cgraph_optimize (void)
/* Double check that all inline clones are gone and that all
function bodies have been released from memory. */
if (flag_unit_at_a_time
- && !dump_enabled_p (TDI_tree_all)
&& !(sorrycount || errorcount))
{
struct cgraph_node *node;
but there may be non-GCable cost of dumping itself.
--
Summary: Using -fdump-tree-optimized causes a huge compile time
memory regression
Product: gcc
Version: 4.1.2
Status: UNCONFIRMED
Keywords: memory-hog
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rguenth at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28463
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug middle-end/28463] [4.0/4.1/4.2 Regression] Using -fdump-tree-optimized causes a huge compile time memory regression
2006-07-23 15:14 [Bug middle-end/28463] New: Using -fdump-tree-optimized causes a huge compile time memory regression rguenth at gcc dot gnu dot org
@ 2006-07-23 15:22 ` steven at gcc dot gnu dot org
2006-07-24 11:43 ` rguenth at gcc dot gnu dot org
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: steven at gcc dot gnu dot org @ 2006-07-23 15:22 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from steven at gcc dot gnu dot org 2006-07-23 15:22 -------
Yup. And a regression too because previous GCCs could dump without sending your
machine to swap space land.
--
steven at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2006-07-23 15:22:25
date| |
Summary|Using -fdump-tree-optimized |[4.0/4.1/4.2 Regression]
|causes a huge compile time |Using -fdump-tree-optimized
|memory regression |causes a huge compile time
| |memory regression
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28463
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug middle-end/28463] [4.0/4.1/4.2 Regression] Using -fdump-tree-optimized causes a huge compile time memory regression
2006-07-23 15:14 [Bug middle-end/28463] New: Using -fdump-tree-optimized causes a huge compile time memory regression rguenth at gcc dot gnu dot org
2006-07-23 15:22 ` [Bug middle-end/28463] [4.0/4.1/4.2 Regression] " steven at gcc dot gnu dot org
@ 2006-07-24 11:43 ` rguenth at gcc dot gnu dot org
2006-09-10 16:59 ` jsm28 at gcc dot gnu dot org
2006-09-10 22:26 ` pinskia at gcc dot gnu dot org
3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu dot org @ 2006-07-24 11:43 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from rguenth at gcc dot gnu dot org 2006-07-24 11:43 -------
Subject: Bug 28463
Author: rguenth
Date: Mon Jul 24 11:42:52 2006
New Revision: 115714
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115714
Log:
2006-07-24 Richard Guenther <rguenther@suse.de>
PR middle-end/28463
* cgraph.c (cgraph_remove_node): Do not check if dumps
are enabled.
* cgraphunit.c (cgraph_optimize): Likewise.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cgraph.c
trunk/gcc/cgraphunit.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28463
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug middle-end/28463] [4.0/4.1/4.2 Regression] Using -fdump-tree-optimized causes a huge compile time memory regression
2006-07-23 15:14 [Bug middle-end/28463] New: Using -fdump-tree-optimized causes a huge compile time memory regression rguenth at gcc dot gnu dot org
2006-07-23 15:22 ` [Bug middle-end/28463] [4.0/4.1/4.2 Regression] " steven at gcc dot gnu dot org
2006-07-24 11:43 ` rguenth at gcc dot gnu dot org
@ 2006-09-10 16:59 ` jsm28 at gcc dot gnu dot org
2006-09-10 22:26 ` pinskia at gcc dot gnu dot org
3 siblings, 0 replies; 5+ messages in thread
From: jsm28 at gcc dot gnu dot org @ 2006-09-10 16:59 UTC (permalink / raw)
To: gcc-bugs
--
jsm28 at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.0.4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28463
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug middle-end/28463] [4.0/4.1/4.2 Regression] Using -fdump-tree-optimized causes a huge compile time memory regression
2006-07-23 15:14 [Bug middle-end/28463] New: Using -fdump-tree-optimized causes a huge compile time memory regression rguenth at gcc dot gnu dot org
` (2 preceding siblings ...)
2006-09-10 16:59 ` jsm28 at gcc dot gnu dot org
@ 2006-09-10 22:26 ` pinskia at gcc dot gnu dot org
3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-09-10 22:26 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from pinskia at gcc dot gnu dot org 2006-09-10 22:26 -------
(In reply to comment #1)
> Yup. And a regression too because previous GCCs could dump without sending your
> machine to swap space land.
Not really, anyways this is fixed now.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
Target Milestone|4.0.4 |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28463
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-09-10 22:26 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-07-23 15:14 [Bug middle-end/28463] New: Using -fdump-tree-optimized causes a huge compile time memory regression rguenth at gcc dot gnu dot org
2006-07-23 15:22 ` [Bug middle-end/28463] [4.0/4.1/4.2 Regression] " steven at gcc dot gnu dot org
2006-07-24 11:43 ` rguenth at gcc dot gnu dot org
2006-09-10 16:59 ` jsm28 at gcc dot gnu dot org
2006-09-10 22:26 ` pinskia at gcc dot gnu dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).