GCC memory consumption increased by recent patch!
gcctest@suse.de
gcctest@suse.de
Mon Sep 13 04:27:00 GMT 2004
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: 17820k
Peak memory use before GGC: 9294k
Peak memory use after GGC: 8606k
Maximum of released memory in single GGC run: 2867k
Garbage: 42475k
Leak: 6107k
Overhead: 5590k
GGC runs: 363
comparing combine.c compilation at -O1 level:
Overall memory needed: 18540k
Peak memory use before GGC: 9573k
Peak memory use after GGC: 8663k
Maximum of released memory in single GGC run: 2067k
Garbage: 78747k
Leak: 6483k
Overhead: 13868k
GGC runs: 589
comparing combine.c compilation at -O2 level:
Overall memory needed: 22076k
Peak memory use before GGC: 12756k
Peak memory use after GGC: 12610k
Maximum of released memory in single GGC run: 2576k
Garbage: 94713k
Leak: 6304k
Overhead: 18777k
GGC runs: 580
comparing combine.c compilation at -O3 level:
Overall memory needed: 23972k
Peak memory use before GGC: 13246k
Peak memory use after GGC: 12610k
Maximum of released memory in single GGC run: 3483k
Garbage: 126026k
Leak: 6852k
Overhead: 24652k
GGC runs: 646
comparing insn-attrtab.c compilation at -O0 level:
Overall memory needed: 132860k
Peak memory use before GGC: 76388k
Peak memory use after GGC: 45185k
Maximum of released memory in single GGC run: 41417k
Garbage: 157790k
Leak: 10620k
Overhead: 19800k
GGC runs: 310
comparing insn-attrtab.c compilation at -O1 level:
Overall memory needed: 151600k
Peak memory use before GGC: 94307k
Peak memory use after GGC: 71401k
Maximum of released memory in single GGC run: 40513k
Garbage: 474239k
Leak: 10968k
Overhead: 84931k
GGC runs: 461
comparing insn-attrtab.c compilation at -O2 level:
Overall memory needed: 237408k
Peak memory use before GGC: 109880k
Peak memory use after GGC: 86974k
Maximum of released memory in single GGC run: 35488k
Garbage: 525180k
Leak: 11150k
Overhead: 95096k
GGC runs: 383
comparing insn-attrtab.c compilation at -O3 level:
Overall memory needed: 237384k
Peak memory use before GGC: 109882k
Peak memory use after GGC: 86975k
Maximum of released memory in single GGC run: 35488k
Garbage: 527525k
Leak: 11223k
Overhead: 95873k
GGC runs: 392
comparing Gerald's testcase PR8361 compilation at -O0 level:
Overall memory needed: 114844k
Peak memory use before GGC: 92008k
Peak memory use after GGC: 90475k
Maximum of released memory in single GGC run: 20896k
Garbage: 270774k
Leak: 58324k
Overhead: 34949k
GGC runs: 552
comparing Gerald's testcase PR8361 compilation at -O1 level:
Overall memory needed: 120284k -> 120268k
Peak memory use before GGC: 96217k
Peak memory use after GGC: 89741k
Maximum of released memory in single GGC run: 20047k
Garbage: 672246k -> 671531k
Leak: 60665k -> 60666k
Overhead: 145158k -> 145201k
GGC runs: 835
comparing Gerald's testcase PR8361 compilation at -O2 level:
Overall memory allocated via mmap and sbrk increased from 121448k to 121700k, overall 0.21%
Amount of produced GGC garbage increased from 726805k to 732760k, overall 0.82%
Overall memory needed: 121448k -> 121700k
Peak memory use before GGC: 96218k
Peak memory use after GGC: 89741k
Maximum of released memory in single GGC run: 20048k
Garbage: 726805k -> 732760k
Leak: 61246k -> 61239k
Overhead: 167636k -> 171766k
GGC runs: 870 -> 866
comparing Gerald's testcase PR8361 compilation at -O3 level:
Overall memory allocated via mmap and sbrk increased from 120080k to 120416k, overall 0.28%
Amount of produced GGC garbage increased from 766821k to 770302k, overall 0.45%
Overall memory needed: 120080k -> 120416k
Peak memory use before GGC: 92007k
Peak memory use after GGC: 90540k
Maximum of released memory in single GGC run: 20814k
Garbage: 766821k -> 770302k
Leak: 61633k -> 61608k
Overhead: 180906k -> 183436k
GGC runs: 851
Head of changelog is:
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog 2004-09-12 21:43:27.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog 2004-09-13 03:37:01.000000000 +0000
@@ -1,3 +1,27 @@
+2004-09-13 Richard Henderson <rth@redhat.com>
+
+ PR tree-opt/10528
+ * tree-inline.c (copy_body_r): Recompute bits for ADDR_EXPR,
+ after copying its argument.
+
+2004-09-13 Joseph S. Myers <jsm@polyomino.org.uk>
+
+ * c-common.c, c-decl.c, c-lex.c, c-objc-common.c, c-opts.c,
+ c-parse.in, c-pragma.c, c-typeck.c: Use %q, %< and %> for quoting
+ in diagnostics. Use %' for English apostrophes.
+ * c-tree.h (ATTRIBUTE_GCC_CDIAG): Define.
+ (pedwarn_c90, pedwarn_c99): Use it.
+ * c-decl.c (lookup_label): Quote label name in diagnostic.
+ * c-parse.in (yyprint): Use ' instead of ` for left quote.
+ * c-typeck.c (warn_for_assignment): Likewise.
+
+2004-09-13 Jan Hubicka <jh@suse.cz>
+
+ * i386.c (x86_schedule): New global variable.
+ (override_options): Disable scheduling when not supported.
+ * i386.h (x86_schedule): Declare.
+ (TARGET_SCHEDULE): New macro.
+
2004-09-12 Richard Henderson <rth@redhat.com>
PR c++/16254
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.
More information about the Gcc-regression
mailing list