This is the mail archive of the
gcc-regression@gcc.gnu.org
mailing list for the GCC project.
GCC memory consumption increased by recent patch!
- From: gcctest at suse dot de
- To: jh at suse dot cz, gcc-regression at gcc dot gnu dot org
- Date: Wed, 02 Feb 2005 03:53:29 +0000
- Subject: GCC memory consumption increased by recent patch!
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: 24637k -> 24645k
Peak memory use before GGC: 9351k
Peak memory use after GGC: 8665k
Maximum of released memory in single GGC run: 2864k
Garbage: 41665k
Leak: 6387k
Overhead: 5772k
GGC runs: 328
comparing combine.c compilation at -O1 level:
Overall memory needed: 25497k -> 25509k
Peak memory use before GGC: 9228k
Peak memory use after GGC: 8733k
Maximum of released memory in single GGC run: 2027k -> 2029k
Garbage: 61218k -> 61220k
Leak: 6749k
Overhead: 9980k -> 9981k
GGC runs: 503
comparing combine.c compilation at -O2 level:
Overall memory needed: 29545k
Peak memory use before GGC: 12663k
Peak memory use after GGC: 12537k
Maximum of released memory in single GGC run: 2596k -> 2597k
Garbage: 79478k -> 79464k
Leak: 6585k
Overhead: 14136k -> 14132k
GGC runs: 516
comparing combine.c compilation at -O3 level:
Amount of memory still referenced at the end of compilation increased from 7074k to 7091k, overall 0.24%
Overall memory needed: 20176k
Peak memory use before GGC: 12794k
Peak memory use after GGC: 12537k
Maximum of released memory in single GGC run: 3407k -> 3409k
Garbage: 107420k -> 107415k
Leak: 7074k -> 7091k
Overhead: 18944k -> 18946k
GGC runs: 582 -> 583
comparing insn-attrtab.c compilation at -O0 level:
Overall memory needed: 114136k
Peak memory use before GGC: 74739k
Peak memory use after GGC: 45485k
Maximum of released memory in single GGC run: 39340k
Garbage: 152660k
Leak: 10976k
Overhead: 19969k
GGC runs: 273
comparing insn-attrtab.c compilation at -O1 level:
Overall memory needed: 124884k -> 124268k
Peak memory use before GGC: 78748k
Peak memory use after GGC: 70095k
Maximum of released memory in single GGC run: 40765k -> 40779k
Garbage: 367812k -> 366122k
Leak: 11353k
Overhead: 69563k -> 69302k
GGC runs: 399 -> 396
comparing insn-attrtab.c compilation at -O2 level:
Overall memory needed: 149040k -> 149044k
Peak memory use before GGC: 98349k
Peak memory use after GGC: 83466k
Maximum of released memory in single GGC run: 39253k -> 39384k
Garbage: 482425k -> 480608k
Leak: 11234k
Overhead: 84837k -> 84551k
GGC runs: 342 -> 341
comparing insn-attrtab.c compilation at -O3 level:
Overall memory needed: 149028k -> 147396k
Peak memory use before GGC: 98351k
Peak memory use after GGC: 83467k
Maximum of released memory in single GGC run: 39254k -> 39385k
Garbage: 483475k -> 481656k
Leak: 11273k -> 11273k
Overhead: 84987k -> 84702k
GGC runs: 348 -> 347
comparing Gerald's testcase PR8361 compilation at -O0 level:
Overall memory needed: 111092k
Peak memory use before GGC: 86885k
Peak memory use after GGC: 85935k
Maximum of released memory in single GGC run: 19282k
Garbage: 245826k
Leak: 55495k
Overhead: 43290k
GGC runs: 367
comparing Gerald's testcase PR8361 compilation at -O1 level:
Overall memory needed: 103689k -> 103701k
Peak memory use before GGC: 85967k
Peak memory use after GGC: 84933k
Maximum of released memory in single GGC run: 18946k
Garbage: 445680k -> 445582k
Leak: 56767k -> 56775k
Overhead: 65545k -> 65538k
GGC runs: 526
comparing Gerald's testcase PR8361 compilation at -O2 level:
Overall memory needed: 104737k
Peak memory use before GGC: 85967k
Peak memory use after GGC: 84933k
Maximum of released memory in single GGC run: 18945k
Garbage: 488587k -> 488583k
Leak: 57372k -> 57372k
Overhead: 75281k -> 75284k
GGC runs: 584
comparing Gerald's testcase PR8361 compilation at -O3 level:
Overall memory needed: 112433k -> 112429k
Peak memory use before GGC: 92707k
Peak memory use after GGC: 86227k
Maximum of released memory in single GGC run: 19713k
Garbage: 504574k -> 504623k
Leak: 57528k -> 57523k
Overhead: 76988k -> 76998k
GGC runs: 569
Head of changelog is:
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog 2005-02-01 21:04:36.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog 2005-02-02 02:52:11.000000000 +0000
@@ -1,3 +1,29 @@
+2005-02-02 Joseph S. Myers <joseph@codesourcery.com>
+
+ PR other/15514
+ * doc/gcov.texi: Fix typo.
+
+2005-02-01 Richard Henderson <rth@redhat.com
+
+ PR target/19680
+ * config/i386/i386.h (MODES_TIEABLE_P): Use ix86_modes_tieable_p.
+ * config/i386/i386.c (ix86_hard_regno_mode_ok): Change return
+ type to bool.
+ (ix86_tieable_integer_mode_p, ix86_modes_tieable_p): New.
+ * config/i386/i386-protos.h: Update.
+
+2005-02-01 Steven Bosscher <stevenb@suse.de>
+
+ PR tree-optimization/19217
+ * tree-cfg.c (verify_expr): Use the data field to see if TP was
+ seen inside a PHI node. Do not do the ADDR_EXPR check if it was.
+ (verify_stmts): Pass (void*)1 as data to verify_expr to signal
+ that it is walking a PHI node.
+
+2005-02-01 Joseph S. Myers <joseph@codesourcery.com>
+
+ * doc/extend.texi (Nested Functions): Update.
+
2005-02-01 Richard Henderson <rth@redhat.com>
PR 19696
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.