This is the mail archive of the gcc-regression@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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: 24669k
    Peak memory use before GGC: 9358k
    Peak memory use after GGC: 8673k
    Maximum of released memory in single GGC run: 2863k
    Garbage: 41664k
    Leak: 6395k
    Overhead: 5772k
    GGC runs: 327

comparing combine.c compilation at -O1 level:
    Overall memory needed: 25517k
    Peak memory use before GGC: 9225k
    Peak memory use after GGC: 8740k
    Maximum of released memory in single GGC run: 2026k
    Garbage: 60428k
    Leak: 6755k
    Overhead: 9931k
    GGC runs: 500

comparing combine.c compilation at -O2 level:
    Overall memory needed: 28897k -> 28893k
    Peak memory use before GGC: 12670k
    Peak memory use after GGC: 12544k
    Maximum of released memory in single GGC run: 2597k
    Garbage: 78374k
    Leak: 6593k
    Overhead: 13974k
    GGC runs: 510

comparing combine.c compilation at -O3 level:
    Overall memory needed: 31545k
    Peak memory use before GGC: 12773k
    Peak memory use after GGC: 12544k
    Maximum of released memory in single GGC run: 3434k
    Garbage: 105579k
    Leak: 7177k
    Overhead: 18736k
    GGC runs: 577

comparing insn-attrtab.c compilation at -O0 level:
    Overall memory needed: 114136k
    Peak memory use before GGC: 74747k
    Peak memory use after GGC: 45493k
    Maximum of released memory in single GGC run: 39340k
    Garbage: 152668k
    Leak: 10984k
    Overhead: 19970k
    GGC runs: 274

comparing insn-attrtab.c compilation at -O1 level:
  Overall memory allocated via mmap and sbrk increased from 123584k to 123908k, overall 0.26%
    Overall memory needed: 123584k -> 123908k
    Peak memory use before GGC: 78747k
    Peak memory use after GGC: 70087k
    Maximum of released memory in single GGC run: 40780k
    Garbage: 369646k
    Leak: 11361k
    Overhead: 69421k
    GGC runs: 398

comparing insn-attrtab.c compilation at -O2 level:
    Overall memory needed: 147644k
    Peak memory use before GGC: 97758k
    Peak memory use after GGC: 83478k
    Maximum of released memory in single GGC run: 39384k
    Garbage: 483554k
    Leak: 11242k
    Overhead: 84511k
    GGC runs: 342

comparing insn-attrtab.c compilation at -O3 level:
    Overall memory needed: 147696k
    Peak memory use before GGC: 97759k
    Peak memory use after GGC: 83480k
    Maximum of released memory in single GGC run: 39384k
    Garbage: 484361k
    Leak: 11279k
    Overhead: 84640k
    GGC runs: 348

comparing Gerald's testcase PR8361 compilation at -O0 level:
    Overall memory needed: 111060k
    Peak memory use before GGC: 87161k
    Peak memory use after GGC: 85900k
    Maximum of released memory in single GGC run: 19511k
    Garbage: 246197k
    Leak: 55513k
    Overhead: 43275k
    GGC runs: 366

comparing Gerald's testcase PR8361 compilation at -O1 level:
    Overall memory needed: 103917k -> 103921k
    Peak memory use before GGC: 86019k
    Peak memory use after GGC: 85119k
    Maximum of released memory in single GGC run: 18950k
    Garbage: 435900k
    Leak: 56846k
    Overhead: 65031k
    GGC runs: 512

comparing Gerald's testcase PR8361 compilation at -O2 level:
    Overall memory needed: 104129k
    Peak memory use before GGC: 86019k
    Peak memory use after GGC: 85119k
    Maximum of released memory in single GGC run: 18950k
    Garbage: 479102k
    Leak: 57414k
    Overhead: 74628k
    GGC runs: 573

comparing Gerald's testcase PR8361 compilation at -O3 level:
    Overall memory needed: 105217k
    Peak memory use before GGC: 87156k
    Peak memory use after GGC: 86199k
    Maximum of released memory in single GGC run: 19400k
    Garbage: 483826k
    Leak: 57577k
    Overhead: 75209k
    GGC runs: 560

Head of changelog is:

--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog	2005-02-22 16:47:48.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog	2005-02-22 17:57:31.000000000 +0000
@@ -4,6 +4,11 @@
 	not available.  Use tail calls wherever possible.
 	(make_edge): Call unchecked_make_edge to create an edge.
 
+	* tree-outof-ssa.c (SSANORM_USE_COALESCE_LIST): Remove.
+	(coalesce_ssa_name): Don't check for
+	SSANORM_USE_COALESCE_LIST.
+	(rewrite_out_of_ssa): Don't use SSANORM_USE_COALESCE_LIST.
+
 2005-02-22  Diego Novillo  <dnovillo@redhat.com>
 
 	* tree-into-ssa.c (rewrite_blocks): Move debug dumps from ...

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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]