gcc 3.3 garbage collector defaults

[Andi Kleen]

> 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