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: Fri, 07 Jan 2005 21:59:32 +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: 24397k -> 24393k
Peak memory use before GGC: 9063k
Peak memory use after GGC: 8377k
Maximum of released memory in single GGC run: 2864k
Garbage: 41736k
Leak: 5862k
Overhead: 5544k
GGC runs: 352
comparing combine.c compilation at -O1 level:
Overall memory needed: 25365k
Peak memory use before GGC: 8951k
Peak memory use after GGC: 8450k
Maximum of released memory in single GGC run: 2024k
Garbage: 66726k
Leak: 6257k
Overhead: 10310k
GGC runs: 545
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: 80658k
Leak: 6081k
Overhead: 14119k
GGC runs: 546
comparing combine.c compilation at -O3 level:
Overall memory needed: 31253k
Peak memory use before GGC: 12635k
Peak memory use after GGC: 12257k
Maximum of released memory in single GGC run: 3347k
Garbage: 109160k
Leak: 6586k
Overhead: 18985k
GGC runs: 613
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: 10432k
Overhead: 20571k
GGC runs: 294
comparing insn-attrtab.c compilation at -O1 level:
Overall memory allocated via mmap and sbrk increased from 127820k to 128492k, overall 0.53%
Overall memory needed: 127820k -> 128492k
Peak memory use before GGC: 83296k
Peak memory use after GGC: 69015k
Maximum of released memory in single GGC run: 40616k
Garbage: 441432k
Leak: 10778k
Overhead: 77163k
GGC runs: 431
comparing insn-attrtab.c compilation at -O2 level:
Overall memory needed: 153116k -> 153120k
Peak memory use before GGC: 99056k
Peak memory use after GGC: 84176k
Maximum of released memory in single GGC run: 41525k
Garbage: 487966k
Leak: 10702k
Overhead: 85263k
GGC runs: 363
comparing insn-attrtab.c compilation at -O3 level:
Overall memory needed: 153128k -> 153268k
Peak memory use before GGC: 99057k
Peak memory use after GGC: 84178k
Maximum of released memory in single GGC run: 41525k
Garbage: 489168k
Leak: 10744k
Overhead: 85423k
GGC runs: 373
comparing Gerald's testcase PR8361 compilation at -O0 level:
Overall memory needed: 110800k
Peak memory use before GGC: 86610k
Peak memory use after GGC: 85642k
Maximum of released memory in single GGC run: 19292k
Garbage: 246356k
Leak: 54976k
Overhead: 43121k
GGC runs: 368
comparing Gerald's testcase PR8361 compilation at -O1 level:
Overall memory needed: 103709k
Peak memory use before GGC: 85639k
Peak memory use after GGC: 84690k
Maximum of released memory in single GGC run: 18904k
Garbage: 466280k
Leak: 56722k
Overhead: 66940k
GGC runs: 554
comparing Gerald's testcase PR8361 compilation at -O2 level:
Overall memory needed: 103765k
Peak memory use before GGC: 85639k
Peak memory use after GGC: 84691k
Maximum of released memory in single GGC run: 18904k
Garbage: 500620k
Leak: 57302k
Overhead: 76402k
GGC runs: 597
comparing Gerald's testcase PR8361 compilation at -O3 level:
Overall memory needed: 111453k
Peak memory use before GGC: 92444k
Peak memory use after GGC: 85893k
Maximum of released memory in single GGC run: 19736k
Garbage: 520600k
Leak: 57619k
Overhead: 78242k
GGC runs: 580
Head of changelog is:
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog 2005-01-07 16:28:30.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog 2005-01-07 20:58:44.000000000 +0000
@@ -1,3 +1,8 @@
+2005-01-07 Jakub Jelinek <jakub@redhat.com>
+
+ * c-common.c (handle_mode_attribute): For ENUMERAL_TYPE, also copy
+ TYPE_MODE.
+
2005-01-07 David Edelsohn <edelsohn@gnu.org>
PR target/13674
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog.cp 2005-01-07 02:02:05.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/cp/ChangeLog 2005-01-07 20:58:48.000000000 +0000
@@ -1,3 +1,8 @@
+2005-01-07 Nathan Sidwell <nathan@codesourcery.com>
+
+ PR c++/19298
+ * pt.c (tsubst_qualified_id): Call convert_from_reference.
+
2005-01-06 Mark Mitchell <mark@codesourcery.com>
PR c++/19244
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.