DMD 1.032 and 2.016 releases

[torhu]

torhu wrote:
> bearophile wrote:
>> Walter Bright:
>>> bearophile wrote:
>>> > At a first test, it seems the compiled executables are 2-3+ times
>>> > bigger than the ones produced by 1.029.
>>> 
>>> Hmm, haven't noticed that.
>> 
>> Here are some exact results:
>> 
>> V. 1.029:
>> libs:     951_324 bytes (with unittests)
>> test.d:   118_300 bytes
>> 
>> V. 1.032:
>> libs:   1_386_012 bytes (with unittests)
>> test.d:   277_020 bytes
>> 
>> Where the libs are my ones, and the test.d is just:
>> 
>> import std.stdio: put = writef, putr = writefln;
>> import std.string: join;
>> void main() {
>>     putr(["ab", "cde"].join(""));
>> }
>> 
>> I'd like to know if someone else can confirm this inflation.
> 
> I recently tried linking my app with DWT built with 1.031 using -lib, 
> and the exe was larger than when using 1.027 and dsss with 
> oneatatime=yes to build DWT.  I didn't look into it, just went back to 
> my 1.027 setup for the time being.  So I think you might be onto something.

I've tested this properly now, with dmd 1.033.  My app grows from 1.9 to 
3.0 MB when linking with a dwt library that's built with dsss and 
oneatatime=yes, versus built with just dmd using the -lib switch.  The 
new discovery here would be that it doesn't matter which compiler 
version is used, it's the -lib switch that's broken somehow.

I haven't looked into this further, but if someone wants to submit a 
minimal test case to bugzilla, be my guest.