From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joern Rennecke <amylaar@cygnus.co.uk>
To: bglenden@aoc.nrao.edu (Brian Glendenning)
Cc: egcs@cygnus.com
Subject: Re: egcs 1.0.2 c++ .o size
Date: Fri, 27 Mar 1998 15:18:00 -0000
Message-id: <199803261534.PAA09782@phal.cygnus.co.uk>
References: <35184EE6.575F538E@aoc.nrao.edu>
X-SW-Source: 1998-03/msg00951.html

> We have a largish (wc -l *.cc *.h = 780k) set of libraries and
> applications (primarily) written in C++. The code is fairly heavily
> templated.
> 
> While trying egcs, I noticed that the .o files and resulting executables
> are about 50% larger than their g++ 2.7.2 counterparts when compiled
> optimized (-O2 in both cases) on solaris. Is this common, or is
> something bad probably happening (e.g. inlines going static).  If
> something bad is probably happening, what are the usual suspects?
> 
> Our binaries are already embarrasingly large - I'd hate to have them
> become 50% more so!

Since 2.7.2 , exception handling has been added.  You can use the
-fno-exceptions option to avoid the overhead of exception handling.