Compiler: Size of generated executable file

[grauzone]

Walter Bright wrote:
> grauzone wrote:
>> (The final executable is almost twice the size as the D2 one too, 
>> although it's questionable how much of the additional size is due to 
>> templates.)
> 
> Finding out why an executable is large is as easy as compiling with 
> -L/map on Windows and -L-map -Lfoo.map on Linux/OSX, and then examining 
> the resulting map file which will tell you each and every symbol in the 
> executable and how large it is.

Yes, but making sense out of the raw data is another thing.