This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ optimization: compile time + memory consumption regressionon gcc3.3 branch
- From: Karel Gardas <kgardas at objectsecurity dot com>
- To: Mike Stump <mstump at apple dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Fri, 28 Feb 2003 22:00:35 +0100 (CET)
- Subject: Re: C++ optimization: compile time + memory consumption regressionon gcc3.3 branch
On Fri, 28 Feb 2003, Mike Stump wrote:
> > Rought comparison:
> >
> > gcc3.2.2: time 20s memory 58MB (reported by top)
> > gcc3.3: time 900s memory about 250MB (reported by top)
>
> If would be helpful to us if you could track this down with something
> like gperf and collect numbers before and after and tell us what
> routines are dying.
I would like to help, but what do you mean by ``before and after''? I can
imagine running c++ compiler with profiling info producing some profile
output, but what's this before and after, I really don't know...
> If not, just include the .ii in the bug report, and hope and pray
> someone else will do the work.
Pray will certainly help, but I'll try to get some numbers for you.
Anyway, I hope someone already described how to compile gcc with profiling
information so I'll be able to find it in the archive...
Thanks,
Karel
--
Karel Gardas kgardas at objectsecurity dot com
ObjectSecurity Ltd. http://www.objectsecurity.com