This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: gcc 3.3 garbage collector defaults
- From: Andi Kleen <ak at suse dot de>
- To: Matt Austern <austern at apple dot com>
- Cc: Zack Weinberg <zack at codesourcery dot com>,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: Tue, 28 Jan 2003 23:07:30 +0100
- Subject: Re: gcc 3.3 garbage collector defaults
- References: <878yx684xp.fsf@egil.codesourcery.com> <DE071295-330B-11D7-9DB0-00039390D9E0@apple.com>
> That's not quite a test of how much memory gets allocated,
> but, if we've turned off the collector, it shouldn't be so very
> different. If allocation patterns have changed, looks like the
> change is something more subtle.
Could it be a cache thrashing due to different usage patterns? Should be
easy to check for using a tool like oprofile on linux, which can
report the hardware cachemiss counters.
Or you could run it in cachegrind.
-Andi