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: Sun, 05 Dec 2004 16:42:26 +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: 25329k
Peak memory use before GGC: 9329k
Peak memory use after GGC: 8641k
Maximum of released memory in single GGC run: 2926k
Garbage: 42603k -> 42601k
Leak: 6088k
Overhead: 5744k -> 5744k
GGC runs: 354
comparing combine.c compilation at -O1 level:
Overall memory needed: 25877k
Peak memory use before GGC: 9200k
Peak memory use after GGC: 8722k
Maximum of released memory in single GGC run: 2063k
Garbage: 68059k -> 68059k
Leak: 6485k
Overhead: 10671k -> 10671k
GGC runs: 547
comparing combine.c compilation at -O2 level:
Overall memory needed: 29977k
Peak memory use before GGC: 12705k
Peak memory use after GGC: 12579k -> 12578k
Maximum of released memory in single GGC run: 2575k
Garbage: 82350k -> 82359k
Leak: 6305k
Overhead: 14872k -> 14872k
GGC runs: 549
comparing combine.c compilation at -O3 level:
Overall memory allocated via mmap and sbrk increased from 20704k to 20732k, overall 0.14%
Amount of memory still referenced at the end of compilation increased from 6817k to 6833k, overall 0.23%
Overall memory needed: 20704k -> 20732k
Peak memory use before GGC: 12993k
Peak memory use after GGC: 12579k -> 12578k
Maximum of released memory in single GGC run: 3412k
Garbage: 111176k -> 111144k
Leak: 6817k -> 6833k
Overhead: 19881k -> 19881k
GGC runs: 615 -> 616
comparing insn-attrtab.c compilation at -O0 level:
Overall memory needed: 118468k
Peak memory use before GGC: 79386k
Peak memory use after GGC: 46137k
Maximum of released memory in single GGC run: 43335k
Garbage: 162034k
Leak: 10610k
Overhead: 21250k
GGC runs: 295
comparing insn-attrtab.c compilation at -O1 level:
Overall memory needed: 132096k
Peak memory use before GGC: 85228k
Peak memory use after GGC: 70033k
Maximum of released memory in single GGC run: 41128k
Garbage: 449315k
Leak: 10956k
Overhead: 79591k
GGC runs: 429
comparing insn-attrtab.c compilation at -O2 level:
Overall memory needed: 154220k
Peak memory use before GGC: 101239k
Peak memory use after GGC: 85446k
Maximum of released memory in single GGC run: 42306k
Garbage: 496293k
Leak: 10876k
Overhead: 87852k
GGC runs: 362
comparing insn-attrtab.c compilation at -O3 level:
Overall memory needed: 154224k
Peak memory use before GGC: 101241k
Peak memory use after GGC: 85448k
Maximum of released memory in single GGC run: 42306k
Garbage: 497581k
Leak: 10923k
Overhead: 88040k
GGC runs: 370
comparing Gerald's testcase PR8361 compilation at -O0 level:
Overall memory needed: 113024k
Peak memory use before GGC: 89585k
Peak memory use after GGC: 88693k
Maximum of released memory in single GGC run: 19771k
Garbage: 249021k
Leak: 57281k
Overhead: 45237k
GGC runs: 361
comparing Gerald's testcase PR8361 compilation at -O1 level:
Overall memory needed: 95584k
Peak memory use before GGC: 88601k
Peak memory use after GGC: 87616k
Maximum of released memory in single GGC run: 19411k
Garbage: 553676k
Leak: 59306k
Overhead: 115278k
GGC runs: 611
comparing Gerald's testcase PR8361 compilation at -O2 level:
Overall memory needed: 95584k
Peak memory use before GGC: 88602k
Peak memory use after GGC: 87617k
Maximum of released memory in single GGC run: 19411k
Garbage: 602697k
Leak: 59897k
Overhead: 137453k
GGC runs: 656
comparing Gerald's testcase PR8361 compilation at -O3 level:
Overall memory needed: 103248k
Peak memory use before GGC: 95700k
Peak memory use after GGC: 88917k
Maximum of released memory in single GGC run: 20229k
Garbage: 642932k
Leak: 60237k
Overhead: 148798k
GGC runs: 650
Head of changelog is:
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog 2004-12-05 05:28:09.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog 2004-12-05 15:36:47.000000000 +0000
@@ -1,3 +1,12 @@
+2004-12-05 Roger Sayle <roger@eyesopen.com>
+
+ * c-typeck.c (c_finish_loop): Improve initial implementations
+ for loops whose conditions are known at compile-time.
+
+2004-12-05 Kazu Hirata <kazu@cs.umass.edu>
+
+ * builtins.c: Fix comment typos.
+
2004-12-04 John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
PR middle-end/18730
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.