Date:	Sat, 26 Aug 2000 11:16:27 +0200 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Ingo Brueckl <ib AT wupperonline DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: version 2.03 binaries size problem
In-Reply-To:	<39a7068b@wupperonline.de>
Message-ID:	<Pine.A41.4.05.10008261110420.12126-100000@ieva06.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 25 Aug 2000, Ingo Brueckl wrote:

> I was using djgpp 2.01 (with gpp2721b and bnu27b) for a project written in
> C++, which resulted in a binary of approx. (stripped) 177 KByte.
> 
> Today I tried version 2.03 (with gpp2952b and bnu2951b) and got a binary size
> of (stripped) 271 KByte, which is a growth of more than 50% for the same
> sources!
> 
> Does anyone know why the size increases that much?! What do I get for the
> extra 100 KByte?

1) If You are not using C++ exceptions and RTTI You can use compiler
   options '-fno-rtti -fno-exceptions' (the default for gcc-2.95.2 is
   -frtti -fexceptions). Try with and without that and see the difference.
   But DON'T ask to make -fno-rtti -fno-exceptions the default (that 
   simply will not happen)

2) Of course You can also strip executables or use UPX to compress them
   additionally (but this not a answer to question)

Andris

- Raw text -