This is the mail archive of the
mailing list for the Cygwin project.
Re: Why MINGW32-EGCC compiled programs so big in size?
- To: "Andrey I. Iliev" <andrei-i at akdi dot ru>
- Subject: Re: Why MINGW32-EGCC compiled programs so big in size?
- From: Mumit Khan <khan at xraylith dot wisc dot edu>
- Date: Fri, 26 Jun 1998 09:31:39 -0500 (CDT)
- 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"
For help on using this list (especially unsubscribing), send a message to
"firstname.lastname@example.org" with one line of text: "help".