GCC memory consumption increased by recent patch!

[gcctest@suse.de]

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: 24665k -> 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: 24509k -> 24513k
    Peak memory use before GGC: 8673k
    Peak memory use after GGC: 8093k
    Maximum of released memory in single GGC run: 2026k
    Garbage: 58442k
    Leak: 6756k
    Overhead: 9864k
    GGC runs: 501

comparing combine.c compilation at -O2 level:
    Overall memory needed: 29149k -> 29137k
    Peak memory use before GGC: 12671k
    Peak memory use after GGC: 12544k
    Maximum of released memory in single GGC run: 2533k
    Garbage: 78281k
    Leak: 6594k
    Overhead: 14171k
    GGC runs: 521

comparing combine.c compilation at -O3 level:
    Overall memory needed: 30849k -> 30869k
    Peak memory use before GGC: 12713k
    Peak memory use after GGC: 12544k
    Maximum of released memory in single GGC run: 3392k
    Garbage: 105939k
    Leak: 7189k
    Overhead: 19036k
    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: 124632k
    Peak memory use before GGC: 78641k
    Peak memory use after GGC: 70036k
    Maximum of released memory in single GGC run: 40781k
    Garbage: 369233k
    Leak: 11361k
    Overhead: 71887k
    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: 486979k
    Leak: 11252k
    Overhead: 87109k
    GGC runs: 342

comparing insn-attrtab.c compilation at -O3 level:
  Overall memory allocated via mmap and sbrk increased from 137824k to 147500k, overall 7.02%
    Overall memory needed: 137824k -> 147500k
    Peak memory use before GGC: 97679k
    Peak memory use after GGC: 83499k
    Maximum of released memory in single GGC run: 39162k
    Garbage: 487787k
    Leak: 11287k
    Overhead: 87239k
    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
    Peak memory use before GGC: 86183k
    Peak memory use after GGC: 85119k
    Maximum of released memory in single GGC run: 18950k
    Garbage: 435088k
    Leak: 56863k
    Overhead: 65172k
    GGC runs: 513

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: 476419k
    Leak: 57427k
    Overhead: 74921k
    GGC runs: 570

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

Head of changelog is:

--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog	2005-03-07 01:59:08.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog	2005-03-07 11:18:37.000000000 +0000
@@ -1,3 +1,20 @@
+2005-03-07  David Billinghurst <David.Billinghurst@riotinto.com>
+
+	* config/i386/cygwin1.c(mingw_scan): Use xstrdup in calls to putenv.
+
+2005-03-07  Joseph S. Myers  <joseph@codesourcery.com>
+
+	* config/ia64/hpux.h (LINK_SPEC): Add -z.
+	* config/ia64/ia64.c (ia64_function_value): Return a REG not a
+	PARALLEL for an empty structure.
+
+2005-03-07  Kazu Hirata  <kazu@cs.umass.edu>
+
+	* fold-const.c (fold_binary): Remove handling of RANGE_EXPR.
+
+	* fold-const.c (fold_binary): Unroll the very first "for"
+	loop.
+
 2005-03-06  David Edelsohn  <edelsohn@gnu.org>
 
 	* config/rs6000/predicates.md (branch_comparison_operator): Remove

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.