This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.3 garbage collector defaults
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Matt Austern <austern at apple dot com>
- Cc: Ziemowit Laski <zlaski at apple dot com>, Neil Booth <neil at daikokuya dot co dot uk>, Benjamin Kosnik <bkoz at redhat dot com>, Andi Kleen <ak at suse dot de>, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Mon, 27 Jan 2003 16:59:46 -0800
- Subject: Re: gcc 3.3 garbage collector defaults
- References: <493CFF37-325A-11D7-B61F-000393B2ABA2@apple.com>
Matt Austern <austern@apple.com> writes:
> When I compare 3.2 and 3.3 on the same file and the same
> machine, 3.3 is much slower than 3.2 and a good part of the
> extra time, according to -ftime-report, is from the gc. If
> those measurements are right (and I think they probably are,
> since several other people report similar results), then
> there aren't a whole lot of possibilities for what caused
> the regression. We now know it wasn't the gc parameters.
> What possibilities haven't we ruled out yet?
My bet would be differing allocation patterns causing the GC to do
more work in 3.3. If you provide me with a test case I can try
various profiling tools and give a more definite answer.
zw