[D-runtime] Committed and uncommitted memory in the GC

[Leandro Lucarella]

In CDGC I completely removed the distinction between committed and
uncommitted memory. This is only useful for Windows AFAIK, but is
currently handled as an integral part of the GC as if it were something
all the OSs use. Besides making the code a little bit more complex, it
has some performance impact (involves some bit manipulation and
reading).

Do you think the price we pay for this is justified or will you be
opened to remove the distinction between committed and uncommitted
memory from the GC? (in Windows, the os_mem_alloc function will
automatically commit the memory too and the deallocation will decommit
it).

-- 
Leandro Lucarella
Senior R&D Developer
Sociomantic Labs GmbH <http://www.sociomantic.com>