From: khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject: Re: Why MINGW32-EGCC compiled programs so big in size?
26 Jun 1998 22:07:30 -0700
Message-ID: <Pine.SUN.3.93.980626093031.16881A-100000.cygnus.gnu-win32@modi.xraylith.wisc.edu>
References: <000601bda052$12910be0$e616e2c2 AT andrei-i DOT akdi DOT ru>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: "Andrey I. Iliev" <andrei-i AT akdi DOT ru>
Cc: "\"GNU-Win32\"" <gnu-win32 AT cygnus DOT com>

On Thu, 25 Jun 1998, Andrey I. Iliev wrote:

> I build some program (source.cpp) using 3 different compilers. 
> Here is file size of executables : 
> 1) VC5                                68096
> 2) BCC 5.02                      69632
> 3) Cygnus b19                   23746
> 4) MINGW32-EGCC      176149 !!!
> 5) MINGW32-GCC           26046
> 
> Can anybody explain why  MINGW32-EGCC produce so big executable?
>  I feel it's probably because MINGW32-EGCC  link statically some libs?
> What libs and why?
> 
> All executables has been compiled with default options: 
> GNU GCC: gcc -o source.exe source.cpp
> VC5: cl source.cpp 
> BCC5: bcc32 source.cpp.  
> 

EGCS will by default include exception and rtti info when building C++
programs. If you don't use either, you can compile with -fno-exceptions
and -fno-rtti to reduce size. Also, have you compared the "stripped"
size?

Mumit

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".