Date:	Thu, 18 Mar 1999 19:09:13 +0100
From:	Ronald de Man <deman AT win DOT tue DOT nl>
To:	pgcc AT delorie DOT com
Subject:	Re: Questions on inlining of code
Message-ID:	<19990318190913.A4377@win.tue.nl>
References:	<199903181530 DOT KAA01307 AT indy3 DOT indy DOT net> <16550 DOT 921776623 AT hurl DOT cygnus DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.4i
In-Reply-To:	<16550.921776623@hurl.cygnus.com>; from Jeffrey A Law on Thu, Mar 18, 1999 at 10:03:43AM -0700
X-Operating-System:	Linux localhost 2.2.3
Reply-To:	pgcc AT delorie DOT com
X-Mailing-List:	pgcc AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, Mar 18, 1999 at 10:03:43AM -0700, Jeffrey A Law wrote:
> 
>   In message <199903181530 DOT KAA01307 AT indy3 DOT indy DOT net>you write:
>   > Two question on inlining of code in egcs/pgcc:
>   > 
>   > 1. Is it possible to disable automatic inlining (compiler switches -O3 or 
>   > -finline) while still respecting the inline declaration in the source code?
>   > I'd like to compile with max optimization (-O6) while avoiding the bloat 
>   > that comes with aggressive inlining of code.  At the same time, though, I 
>   > don't want to disabled the inlining of code explicitly declared as such.
> The only difference between -O2 and -On for n > 2 is automatic function
> inlining.  So, just use -O2.

Which is from the man file, but is not true for pgcc (is it true for egcs?).

Would -fno-inline not do what you want? I think that -fno-inline is
merely a switch to disable -finline, so that it does not affect functions
that are explicitly declared inline. So try -O6 -fno-inline.

Ronald

- Raw text -