This is the mail archive of the
gcc-regression@gcc.gnu.org
mailing list for the GCC project.
A recent patch increased GCC's memory consumption!
- From: gcctest at suse dot de
- To: jh at suse dot cz, gcc-regression at gcc dot gnu dot org
- Date: Wed, 31 Aug 2005 17:05:55 +0000
- Subject: A recent patch increased GCC's memory consumption!
Hi,
I am a friendly script caring about memory consumption in GCC. Please
contact jh@suse.cz if something is going wrong.
Comparing memory consumption on compilation of combine.i, insn-attrtab.i,
and generate-3.4.ii I got:
comparing combine.c compilation at -O0 level:
Overall memory needed: 24833k -> 24841k
Peak memory use before GGC: 9590k
Peak memory use after GGC: 8937k
Maximum of released memory in single GGC run: 2737k
Garbage: 40070k
Leak: 6698k
Overhead: 5787k
GGC runs: 316
comparing combine.c compilation at -O1 level:
Overall memory needed: 26812k
Peak memory use before GGC: 17359k
Peak memory use after GGC: 17173k
Maximum of released memory in single GGC run: 2373k
Garbage: 60344k -> 60341k
Leak: 7084k
Overhead: 7591k -> 7591k
GGC runs: 385
comparing combine.c compilation at -O2 level:
Overall memory needed: 26812k
Peak memory use before GGC: 17361k
Peak memory use after GGC: 17173k
Maximum of released memory in single GGC run: 2456k
Garbage: 77890k -> 77878k
Leak: 7476k
Overhead: 10123k -> 10121k
GGC runs: 456 -> 457
comparing combine.c compilation at -O3 level:
Amount of memory still referenced at the end of compilation increased from 7548k to 7560k, overall 0.16%
Overall memory needed: 26812k
Peak memory use before GGC: 18479k
Peak memory use after GGC: 18109k
Maximum of released memory in single GGC run: 3367k
Garbage: 111044k -> 111036k
Leak: 7548k -> 7560k
Overhead: 13950k -> 13950k
GGC runs: 515
comparing insn-attrtab.c compilation at -O0 level:
Overall memory needed: 80920k
Peak memory use before GGC: 69464k
Peak memory use after GGC: 45002k
Maximum of released memory in single GGC run: 36248k
Garbage: 146330k
Leak: 10091k
Overhead: 19790k
GGC runs: 250
comparing insn-attrtab.c compilation at -O1 level:
Overall memory needed: 111888k
Peak memory use before GGC: 94162k
Peak memory use after GGC: 83709k
Maximum of released memory in single GGC run: 32587k
Garbage: 290093k -> 290092k
Leak: 10077k
Overhead: 36723k -> 36723k
GGC runs: 245
comparing insn-attrtab.c compilation at -O2 level:
Overall memory needed: 126408k
Peak memory use before GGC: 113395k
Peak memory use after GGC: 83671k
Maximum of released memory in single GGC run: 32273k
Garbage: 376144k -> 376143k
Leak: 10190k
Overhead: 48541k -> 48541k
GGC runs: 273
comparing insn-attrtab.c compilation at -O3 level:
Overall memory needed: 126456k
Peak memory use before GGC: 113417k
Peak memory use after GGC: 83695k
Maximum of released memory in single GGC run: 32593k
Garbage: 376704k -> 376704k
Leak: 10208k
Overhead: 48692k -> 48692k
GGC runs: 275
comparing Gerald's testcase PR8361 compilation at -O0 level:
Overall memory needed: 118612k
Peak memory use before GGC: 95329k
Peak memory use after GGC: 94374k
Maximum of released memory in single GGC run: 20170k
Garbage: 226745k
Leak: 49361k
Overhead: 36904k
GGC runs: 343
comparing Gerald's testcase PR8361 compilation at -O1 level:
Overall memory needed: 105988k
Peak memory use before GGC: 95934k
Peak memory use after GGC: 93445k
Maximum of released memory in single GGC run: 20638k
Garbage: 576046k -> 576047k
Leak: 55657k
Overhead: 68544k -> 68543k
GGC runs: 494 -> 493
comparing Gerald's testcase PR8361 compilation at -O2 level:
Overall memory needed: 106936k -> 106908k
Peak memory use before GGC: 95934k
Peak memory use after GGC: 93446k
Maximum of released memory in single GGC run: 20638k
Garbage: 662684k -> 662706k
Leak: 56487k -> 56486k
Overhead: 80312k -> 80314k
GGC runs: 557 -> 556
comparing Gerald's testcase PR8361 compilation at -O3 level:
Overall memory needed: 110504k -> 110216k
Peak memory use before GGC: 97416k
Peak memory use after GGC: 94521k
Maximum of released memory in single GGC run: 21144k
Garbage: 717126k -> 717190k
Leak: 57458k
Overhead: 85177k -> 85178k
GGC runs: 564
Head of the ChangeLog is:
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog 2005-08-31 11:19:15.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog 2005-08-31 15:56:19.000000000 +0000
@@ -1,3 +1,16 @@
+2005-08-31 Fariborz Jahanian <fjahanian@apple.com>
+
+ * expr.c (expand_expr_real_1): Compare size of address
+ mode to target's address mode size in deciding expansion of
+ the constant address.
+
+2005-08-31 Richard Guenther <rguenther@suse.de>
+
+ PR middle-end/23477
+ * expr.c (all_zeros_p): New function.
+ (expand_expr_real_1): Handle the case of an all-zero
+ non-addressable constructor separately.
+
2005-08-31 Adrian Straetling <straetling@de.ibm.com>
* builtins.c: (expand_builtin_strcpy, expand_builtin_strcat): Change
@@ -25,13 +38,13 @@
* config/i386/i386.c (ix86_expand_vector_init_one_var): Don't modify
parts of 'vals'.
-2005-08-18 Andrew Pinski <pinskia@physics.uc.edu>
+2005-08-29 Andrew Pinski <pinskia@physics.uc.edu>
PR middle-end/23408
* ipa-inline.c (cgraph_decide_inlining_incrementally): Remove the
call to ggc_collect.
-2005-08-18 Paolo Bonzini <bonzini@gnu.org>
+2005-08-29 Paolo Bonzini <bonzini@gnu.org>
PR bootstrap/21268
* Makefile.in (ALL_CPPFLAGS): Include $(INCLUDES) at the
--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog.cp 2005-08-31 11:19:18.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/cp/ChangeLog 2005-08-31 15:56:21.000000000 +0000
@@ -1,3 +1,9 @@
+2005-08-31 Andrew Pinski <pinskia@physics.uc.edu>
+
+ PR obj-c++/23640
+ * decl2.c (cp_finish_file): If this is obj-c++ and we need a static
+ init, call generate_ctor_or_dtor_function.
+
2005-08-31 Volker Reichelt <reichelt@igpm.rwth-aachen.de>
PR c++/13377
The results can be reproduced by building a 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.
Your testing script.