GCC memory consumption decreased by recent patch

gcctest@suse.de gcctest@suse.de
Fri Mar 4 07:48:00 GMT 2005


Hi,
Comparing memory consumption on compilation of combine.i and generate-3.4.ii I got:


comparing combine.c compilation at -O0 level:
    Overall memory needed: 24661k
    Peak memory use before GGC: 9359k
    Peak memory use after GGC: 8673k
    Maximum of released memory in single GGC run: 2865k
    Garbage: 41675k
    Leak: 6395k
    Overhead: 5772k
    GGC runs: 327

comparing combine.c compilation at -O1 level:
    Overall memory needed: 24485k -> 24477k
    Peak memory use before GGC: 8673k
    Peak memory use after GGC: 8093k
    Maximum of released memory in single GGC run: 2026k
    Garbage: 58507k
    Leak: 6756k
    Overhead: 9891k
    GGC runs: 500

comparing combine.c compilation at -O2 level:
    Overall memory needed: 29149k -> 29141k
    Peak memory use before GGC: 12671k
    Peak memory use after GGC: 12544k
    Maximum of released memory in single GGC run: 2533k
    Garbage: 78197k
    Leak: 6595k
    Overhead: 14161k
    GGC runs: 520

comparing combine.c compilation at -O3 level:
    Overall memory needed: 30833k -> 30821k
    Peak memory use before GGC: 12714k
    Peak memory use after GGC: 12544k
    Maximum of released memory in single GGC run: 3391k
    Garbage: 105804k
    Leak: 7174k
    Overhead: 19019k
    GGC runs: 583

comparing insn-attrtab.c compilation at -O0 level:
    Overall memory needed: 114212k
    Peak memory use before GGC: 74821k
    Peak memory use after GGC: 45494k
    Maximum of released memory in single GGC run: 39413k
    Garbage: 152830k
    Leak: 10984k
    Overhead: 19970k
    GGC runs: 273

comparing insn-attrtab.c compilation at -O1 level:
    Overall memory needed: 124600k
    Peak memory use before GGC: 78641k
    Peak memory use after GGC: 70036k
    Maximum of released memory in single GGC run: 40782k
    Garbage: 369270k
    Leak: 11361k
    Overhead: 71894k
    GGC runs: 398

comparing insn-attrtab.c compilation at -O2 level:
    Overall memory needed: 148936k
    Peak memory use before GGC: 97678k
    Peak memory use after GGC: 83497k
    Maximum of released memory in single GGC run: 39163k
    Garbage: 486952k
    Leak: 11252k
    Overhead: 87104k
    GGC runs: 342

comparing insn-attrtab.c compilation at -O3 level:
  Ovarall memory allocated via mmap and sbrk decreased from 147500k to 137824k, overall -7.02%
    Overall memory needed: 147500k -> 137824k
    Peak memory use before GGC: 97679k
    Peak memory use after GGC: 83499k
    Maximum of released memory in single GGC run: 39162k
    Garbage: 487762k
    Leak: 11287k
    Overhead: 87234k
    GGC runs: 348

comparing Gerald's testcase PR8361 compilation at -O0 level:
    Overall memory needed: 111952k
    Peak memory use before GGC: 87325k
    Peak memory use after GGC: 85900k
    Maximum of released memory in single GGC run: 19511k
    Garbage: 246370k
    Leak: 55513k
    Overhead: 43275k
    GGC runs: 366

comparing Gerald's testcase PR8361 compilation at -O1 level:
    Overall memory needed: 104033k -> 104037k
    Peak memory use before GGC: 86183k
    Peak memory use after GGC: 85119k
    Maximum of released memory in single GGC run: 18950k
    Garbage: 434991k
    Leak: 56864k
    Overhead: 65164k
    GGC runs: 512

comparing Gerald's testcase PR8361 compilation at -O2 level:
    Overall memory needed: 104249k
    Peak memory use before GGC: 86184k
    Peak memory use after GGC: 85119k
    Maximum of released memory in single GGC run: 18951k
    Garbage: 477138k
    Leak: 57427k
    Overhead: 74970k
    GGC runs: 569

comparing Gerald's testcase PR8361 compilation at -O3 level:
    Overall memory needed: 105349k
    Peak memory use before GGC: 87323k
    Peak memory use after GGC: 86199k
    Maximum of released memory in single GGC run: 19400k
    Garbage: 482585k
    Leak: 57637k
    Overhead: 75706k
    GGC runs: 557

Head of changelog is:

--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog	2005-03-04 02:32:27.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog	2005-03-04 06:49:34.000000000 +0000
@@ -1,3 +1,45 @@
+2005-03-04  Andrew Pinski  <pinskia@physics.uc.edu>
+
+	Revert for now:
+	2005-03-03  James A. Morrison  <phython@gcc.gnu.org>
+	PR tree-optimization/15784
+	* fold-const.c (fold): Fold ~A + 1 to -1.  Fold -A - 1
+	and -1 - A to ~A.
+
+2005-03-04  Ben Elliston  <bje@au.ibm.com>
+
+	* gcc.c (option_map): Add --coverage.
+	(LINK_COMMAND_SPEC): Pass -lgcov for `coverage'.
+	(cc1_options): Pass -fprofile-arcs -ftest-coverage for `coverage'.
+	* config/darwin.h: Pass -lgcov for `coverage'.
+	* doc/invoke.texi (Debugging Options): Document --coverage.
+
+2005-03-04  Kazu Hirata  <kazu@cs.umass.edu>
+
+	* gcse.c (bypass_block): Use find_edge wherever possible.
+
+2005-03-03  Daniel Berlin <dberlin@dbrelin.org>
+
+	Fix PR debug/20253
+	
+	* c-opts.c (c_common_parse_file): Call start_source_file
+	and end_source_file at the approriate times.
+
+	* dwarf2out.c (dwarf2out_finish): Don't auto-end
+	the main file, it will be done for us now.
+	
+2005-03-04  Kazu Hirata  <kazu@cs.umass.edu>
+
+	* fold-const.c (fold_ternary): New.
+	(fold): Call fold_ternary on ternary expressions.  Remove
+	handling of ternary expressions.
+
+2005-03-03  James A. Morrison  <phython@gcc.gnu.org>
+
+	PR tree-optimization/15784
+	* fold-const.c (fold): Fold ~A + 1 to -1.  Fold -A - 1
+	and -1 - A to ~A.
+
 2005-03-03  David Edelsohn  <edelsohn@gnu.org>
 
 	* config/rs6000/predicates.md (branch_comparison_operator):

I am friendly script caring about memory consumption in GCC.  Please contact
jh@suse.cz if something is going wrong.

The results can be reproduced by building compiler with
--enable-gather-detailed-mem-stats targetting x86-64 and compiling preprocessed
combine.c or testcase from PR8632 with:

-fmem-report --param=ggc-min-heapsize=1024 --param=ggc-min-expand=1 -Ox -Q

The memory consumption summary appears in the dump after detailed listing of
the places they are allocated in.  Peak memory consumption is actually computed
by looking for maximal value in {GC XXXX -> YYYY} report.

Yours testing script.



More information about the Gcc-regression mailing list