This is the mail archive of the gcc@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]

Re: A preliminary result of fold_buildN (memory usage included)

From: Mark Mitchell <mark at codesourcery dot com>
To: Kazu Hirata <kazu at cs dot umass dot edu>
Cc: gcc at gcc dot gnu dot org, dvorakz at suse dot cz, roger at eyesopen dot com
Date: Mon, 07 Mar 2005 20:01:53 -0800
Subject: Re: A preliminary result of fold_buildN (memory usage included)
Organization: CodeSourcery, LLC
References: <20050307.021950.71109921.kazu@cs.umass.edu>

Kazu Hirata wrote:

Hi,

Here is a preliminary result for fold_buildN from my personal tree.  I
compiled cc1-i files with ./cc1 -quiet -O2 -fomit-frame-pointer
-fmem-report -o /dev/null.  I used --enable-gather-detailed-mem-stats
to see how many nodes and bytes we are allocating for trees.  (Thanks
Honza!)  I then summed up the memory usage of trees.

            original       patched   diff%
#nodes    24,234,589    23,577,245 -2.712%
#bytes 1,228,797,315 1,205,528,427 -1.893%

As far as compile time, I consistently see improvements of 0.1% or a
bit more.

That's good. I think that in situations where you're using PCH, you'll likely see a better improvement, as you'll need to access fewer PCH pages when later on. Thanks for working on this cleanup; it's a long-standing issue.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304

References:
- A preliminary result of fold_buildN (memory usage included)
  - From: Kazu Hirata

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