Compiler: Size of generated executable file

Walter Bright newshound1 at digitalmars.com
Sat Jan 9 13:28:19 PST 2010


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.



More information about the Digitalmars-d mailing list