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: Thu, 30 Dec 2004 00:22:35 +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: 24385k -> 24389k
Peak memory use before GGC: 9063k
Peak memory use after GGC: 8377k
Maximum of released memory in single GGC run: 2864k
Garbage: 41736k
Leak: 5863k
Overhead: 5545k
GGC runs: 352
comparing combine.c compilation at -O1 level:
Overall memory needed: 25361k -> 25365k
Peak memory use before GGC: 8954k -> 8951k
Peak memory use after GGC: 8450k
Maximum of released memory in single GGC run: 2025k -> 2024k
Garbage: 67051k -> 67057k
Leak: 6258k
Overhead: 10335k -> 10339k
GGC runs: 544
comparing combine.c compilation at -O2 level:
Overall memory needed: 28849k -> 28853k
Peak memory use before GGC: 12383k
Peak memory use after GGC: 12257k
Maximum of released memory in single GGC run: 2533k
Garbage: 80978k -> 80977k
Leak: 6082k
Overhead: 14148k -> 14148k
GGC runs: 547
comparing combine.c compilation at -O3 level:
Overall memory needed: 31317k -> 31329k
Peak memory use before GGC: 12657k
Peak memory use after GGC: 12257k
Maximum of released memory in single GGC run: 3348k -> 3347k
Garbage: 109624k -> 109648k
Leak: 6604k -> 6603k
Overhead: 19019k -> 19019k
GGC runs: 614
comparing insn-attrtab.c compilation at -O0 level:
Overall memory needed: 117268k
Peak memory use before GGC: 77779k
Peak memory use after GGC: 45259k
Maximum of released memory in single GGC run: 42606k
Garbage: 159302k
Leak: 10433k
Overhead: 20572k
GGC runs: 294
comparing insn-attrtab.c compilation at -O1 level:
Overall memory allocated via mmap and sbrk increased from 128092k to 128504k, overall 0.32%
Overall memory needed: 128092k -> 128504k
Peak memory use before GGC: 83296k
Peak memory use after GGC: 69015k
Maximum of released memory in single GGC run: 40616k
Garbage: 441503k
Leak: 10779k
Overhead: 77179k
GGC runs: 430
comparing insn-attrtab.c compilation at -O2 level:
Overall memory needed: 153256k -> 153116k
Peak memory use before GGC: 99056k
Peak memory use after GGC: 84176k
Maximum of released memory in single GGC run: 41527k
Garbage: 488031k
Leak: 10703k
Overhead: 85275k
GGC runs: 363
comparing insn-attrtab.c compilation at -O3 level:
Overall memory needed: 153132k -> 153128k
Peak memory use before GGC: 99057k
Peak memory use after GGC: 84178k
Maximum of released memory in single GGC run: 41526k
Garbage: 489303k
Leak: 10745k
Overhead: 85439k
GGC runs: 373
comparing Gerald's testcase PR8361 compilation at -O0 level:
Overall memory needed: 110796k
Peak memory use before GGC: 86609k
Peak memory use after GGC: 85641k
Maximum of released memory in single GGC run: 19292k
Garbage: 242966k
Leak: 54798k
Overhead: 42337k
GGC runs: 365
comparing Gerald's testcase PR8361 compilation at -O1 level:
Overall memory needed: 103701k
Peak memory use before GGC: 85639k
Peak memory use after GGC: 84690k
Maximum of released memory in single GGC run: 18904k
Garbage: 473955k -> 474023k
Leak: 56726k
Overhead: 67427k -> 67433k
GGC runs: 559
comparing Gerald's testcase PR8361 compilation at -O2 level:
Overall memory needed: 103761k
Peak memory use before GGC: 85639k
Peak memory use after GGC: 84691k
Maximum of released memory in single GGC run: 18904k
Garbage: 508534k -> 508498k
Leak: 57306k
Overhead: 76940k -> 76947k
GGC runs: 605
comparing Gerald's testcase PR8361 compilation at -O3 level:
Overall memory needed: 111445k -> 111441k
Peak memory use before GGC: 92444k
Peak memory use after GGC: 85893k
Maximum of released memory in single GGC run: 19736k
Garbage: 530344k -> 530309k
Leak: 57641k -> 57625k
Overhead: 78803k -> 78780k
GGC runs: 585 -> 586
Head of changelog is:
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog 2004-12-29 18:00:33.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog 2004-12-29 23:21:00.000000000 +0000
@@ -1,3 +1,8 @@
+2004-12-29 Jeff Law <law@redhat.com>
+
+ * tree-outof-ssa.c (insert_backedge_copies): New function.
+ (rewrite_out_of_ssa): Use it.
+
2004-12-29 Ira Rosen <irar@il.ibm.com>
PR tree-optimization/18179
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.