On Tuesday, 12-06-1994  Gary Chambers wrote to All about "EXE Size" as
follows:

GC> Why, apparently, are the resultant .EXE files created by 
GC> Borland C++ for OS/2 1.5 so much larger than their CSet/2 
GC> counterparts?  For example, the disk that accompanies Real 
GC> World Programming for OS/2 2.11 contains examples compiled 
GC> with CSet/2.  When I compile the same exact source code 
GC> with my Borland compiler, the EXE skyrockets in size.  Is 
GC> there something (aside from linking the DLL version of the 
GC> RTL) I can do to decrease this size?  Thanks...

Hi Gary,

Well, for starters, the Borland compiler does produce signifcantly
less efficient object code than does the IBM. But the "gotcha" in 1.5
was exception handling. It seems that even if you don't try to handle
exceptions the compiler will still produce code to introduce the
run-time support for it. Try using -x- as a compiler option (it's
case-sensitive). Also, -RT- will switch off RTTI.

It seems these are switched on for C as well as C++, just in case a
C++ module gets hauled in during the link.

The best solution is to get IBM C Set ++ and use that, though.

Regards

Dave

 * KWQ/2 1.2g * I thunk therefore I am ..... 32-bit compiler
--- Maximus/2 2.02