Re: [TCLUG:11831] Binary bloat with egcs or gcc-2.95.2

["Thomas T. Veldhouse" <veldy@visi.com>]

Yep, that was the majority of it.  When I looked - configure for most
programs seems to default to setting the CFLAGS="-g -O2".  I simply set my
environment variable (before I run configure) CFLAGS="-O2 -pipe" and all is
well.

Tom Veldhouse
veldy@visi.com

----- Original Message -----
From: "Jon Schewe" <jpschewe@eggplant.mtu.net>
To: <tclug-list@mn-linux.org>
Sent: Sunday, January 02, 2000 5:22 PM
Subject: Re: [TCLUG:11831] Binary bloat with egcs or gcc-2.95.2


> "Thomas T. Veldhouse" wrote:
> >
> > Does anybody know how to get rid of the code bloat caused by compile
under
> > egcs-1.1.2 (or even earlier) and gcc-2.95.2?
> >
> > What I mean is that I just compiled the 2.9.1.25 binutils and my
previous
> > version was the same (except it was the default supplied by Slackware).
The
> > binary, /usr/bin/as, is many times larger than the original one.  It
> > certainly seems faster, but I am not sure it is a good price to pay.  I
have
> > not found any command line switches that "magically" turn off code
bloat -
> > but there must be one somewhere.  Slackware managed to do it, right?
> >
> Perhaps you need to strip the binary.  This takes off the symbol table
> and a few other things you only need for debugging.  Just run strip on
> the binary.
> --
> Jon Schewe
> http://eggplant.mtu.net/~jpschewe
> schewe@tcfreenet.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
>