Concern about dmd memory usage on win32

[Jonathan M Davis]

On Friday, December 07, 2012 18:18:43 monarch_dodra wrote:
> I had actually been through this before, and someone told me
> about that. The problem at this point is that this isn't even an
> option anymore, since std/algorithm.d is in a group *alone*.

Then I'd have two suggestions then:

1. Figure out which tests are too expensive. Either disable them or make them 
less expensive. If we can't test as much as we need to right now, then the 
less critical tests will just need to be disabled as ugly as that may be.

2. version stuff. Either specifically version some of it out on Windows (or 
maybe just 32-bit Windows now that we have 64-bit Windows), or put some of the 
less critical stuff in version blocks that can be explicitly enabled by someone 
working on Phobos.

The two should probably be combined though. Figure out which tests are 
problematic and version out the less critical ones on 32-bit Windows. Then you 
can create a bug report for those tests specifically and anyone working on the 
memory problem with have somethingh specific to run.

Much of std.datetime's tests used to have to be disabled with version blocks 
on Windows until the compiler was improved enough and/or the tests were 
adjusted enough that they could be run on Windows (adjusting the makefile 
probably helped as well).

Templates and CTFE are particularly expensive, so fantastic tricks like using 
foreach with TypeTuple can really cost a lot with dmd's current memory issues, 
and std.algorithm may just not be able to afford some of the better tests right 
now as much as that sucks.

- Jonathan M Davis