Some aspect of GCC memory consumption increased by recent patch

[Nathan Sidwell]

Jan Hubicka wrote:

>>BTW, is forwarding the memory usage info from the point of call of the 
>>vector
>>api functions the right thing? (Rather than merely indicate the vector API
>>function itself?)
> 
> In general, I think it is quite important to know who is consuming the
> memory so it is better to forward the info. However vecotors, like
> varrays, are bit special by the fact that singe vector is usually grown
> at several places so the overall memory consumption of each vector gets
> distributed into many lines making it more dificult to track down.
> 
> Perhaps it would be best to have specialized statistics like we do have
> for varrays, but I don't think it is very critical at the moment.

Ok.  I'll leave it for now.  It's not quite clear to me as to how
to (simply) implement the required static members that'd be needed to do this
on a per-vector-type bases.  If we can rely on uninitialized global
declarations being mergeable tentative definitions, it'd be simple, but I
think we cannot assume that.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk