Compile-time memory footprint of std.algorithm

[Iain Buclaw via Digitalmars-d]

On 23 April 2014 22:24, Iain Buclaw <ibuclaw at gdcproject.org> wrote:
> On 23 April 2014 21:55, "Nordlöw" <digitalmars-d at puremagic.com> wrote:
>>> Maybe we should investigate where the memory is going first before
>>> planning our attack :-)
>>
>>
>> I agree. Tool anyone?
>
> I'm using valgrind - may take a while to process and merge them all.
> I'll post an update in the morning.

I was amazed to see some small losses in the glue (that I'll be
dealing with), but by and large the worst culprits were all the
syntaxCopy'ing done in Template semantic analysis.

The resultant assembly file emitted by gdc is 83MB in size, so I think
it is impossible to not have a large memory consumption here.  The
stats file is 100MB (39k reported leaks) and I'm not sure just what to
do with it yet.