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!

From: gcctest at suse dot de
To: jh at suse dot cz, gcc-regression at gcc dot gnu dot org
Date: Thu, 09 Dec 2004 18:12:08 +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: 25253k
    Peak memory use before GGC: 9310k
    Peak memory use after GGC: 8624k
    Maximum of released memory in single GGC run: 2912k
    Garbage: 42433k
    Leak: 6088k
    Overhead: 5717k
    GGC runs: 353

comparing combine.c compilation at -O1 level:
    Overall memory needed: 26165k -> 26125k
    Peak memory use before GGC: 9199k
    Peak memory use after GGC: 8723k
    Maximum of released memory in single GGC run: 2062k
    Garbage: 67984k -> 67984k
    Leak: 6484k
    Overhead: 10665k -> 10665k
    GGC runs: 545

comparing combine.c compilation at -O2 level:
    Overall memory needed: 29969k -> 29965k
    Peak memory use before GGC: 12705k
    Peak memory use after GGC: 12578k
    Maximum of released memory in single GGC run: 2574k
    Garbage: 82176k -> 82170k
    Leak: 6299k
    Overhead: 14822k
    GGC runs: 547

comparing combine.c compilation at -O3 level:
  Overall memory allocated via mmap and sbrk increased from 20720k to 20756k, overall 0.17%
    Overall memory needed: 20720k -> 20756k
    Peak memory use before GGC: 12987k
    Peak memory use after GGC: 12578k
    Maximum of released memory in single GGC run: 3411k
    Garbage: 111130k -> 111082k
    Leak: 6848k -> 6832k
    Overhead: 19898k
    GGC runs: 614

comparing insn-attrtab.c compilation at -O0 level:
    Overall memory needed: 118468k
    Peak memory use before GGC: 79386k
    Peak memory use after GGC: 46137k
    Maximum of released memory in single GGC run: 43335k
    Garbage: 161982k
    Leak: 10609k
    Overhead: 21242k
    GGC runs: 296

comparing insn-attrtab.c compilation at -O1 level:
    Overall memory needed: 132256k
    Peak memory use before GGC: 85238k
    Peak memory use after GGC: 70037k
    Maximum of released memory in single GGC run: 41132k
    Garbage: 449300k
    Leak: 10955k
    Overhead: 79597k
    GGC runs: 430

comparing insn-attrtab.c compilation at -O2 level:
    Overall memory needed: 154184k
    Peak memory use before GGC: 101250k
    Peak memory use after GGC: 85450k
    Maximum of released memory in single GGC run: 42175k
    Garbage: 496321k -> 496321k
    Leak: 10875k
    Overhead: 87871k
    GGC runs: 364

comparing insn-attrtab.c compilation at -O3 level:
    Overall memory needed: 154200k
    Peak memory use before GGC: 101251k
    Peak memory use after GGC: 85452k
    Maximum of released memory in single GGC run: 42175k
    Garbage: 497599k -> 497599k
    Leak: 10920k
    Overhead: 88052k
    GGC runs: 372

comparing Gerald's testcase PR8361 compilation at -O0 level:
    Overall memory needed: 113408k
    Peak memory use before GGC: 89927k
    Peak memory use after GGC: 89033k
    Maximum of released memory in single GGC run: 19901k
    Garbage: 248762k
    Leak: 57794k
    Overhead: 45380k
    GGC runs: 362

comparing Gerald's testcase PR8361 compilation at -O1 level:
    Overall memory needed: 95924k
    Peak memory use before GGC: 88924k
    Peak memory use after GGC: 87950k
    Maximum of released memory in single GGC run: 19406k
    Garbage: 553024k -> 552814k
    Leak: 59829k
    Overhead: 115300k -> 115300k
    GGC runs: 611

comparing Gerald's testcase PR8361 compilation at -O2 level:
    Overall memory needed: 95924k
    Peak memory use before GGC: 88924k
    Peak memory use after GGC: 87951k
    Maximum of released memory in single GGC run: 19405k
    Garbage: 601999k -> 601727k
    Leak: 60410k
    Overhead: 137350k -> 137348k
    GGC runs: 653

comparing Gerald's testcase PR8361 compilation at -O3 level:
    Overall memory needed: 98420k -> 98404k
    Peak memory use before GGC: 90321k
    Peak memory use after GGC: 88783k
    Maximum of released memory in single GGC run: 20095k
    Garbage: 642094k -> 641849k
    Leak: 60742k
    Overhead: 148779k -> 148778k
    GGC runs: 648 -> 646

Head of changelog is:

--- /usr/src/SpecTests/sandbox-britten-memory/x86_64/mem-result/ChangeLog	2004-12-09 11:15:57.000000000 +0000
+++ /usr/src/SpecTests/sandbox-britten-memory/gcc/gcc/ChangeLog	2004-12-09 17:08:15.000000000 +0000
@@ -1,3 +1,15 @@
+2004-12-09  Andrew Pinski  <pinskia@physics.uc.edu>
+
+	PR tree-opt/18904
+	* tree-chrec.c (chrec_convert): Use fold_convert
+	instead of convert.
+
+2004-12-09  Matt Rice  <ratmice@yahoo.com>
+
+	PR preprocessor/18102
+	* c-incpath.c (remove_duplicates): Check for construct
+	equality.
+
 2004-12-09  Dorit Naishlos  <dorit@il.ibm.com>
 
 	* genopinit.c (vec_realign_store_optab): Initialization removed.

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]