delorie.com/archives/browse.cgi | search |
To: | "Steve Snyder" <ssnyder AT indy DOT net> |
cc: | "EGCS Mailing List" <egcs AT cygnus DOT com>, |
"PGCC Mailing List" <pgcc AT delorie DOT com> | |
Subject: | Re: Questions on inlining of code |
In-reply-to: | Your message of Thu, 18 Mar 1999 10:29:24 MST. |
<199903181530 DOT KAA01307 AT indy3 DOT indy DOT net> | |
Date: | Thu, 18 Mar 1999 10:03:43 -0700 |
Message-ID: | <16550.921776623@hurl.cygnus.com> |
From: | Jeffrey A Law <law AT hurl DOT cygnus DOT com> |
Reply-To: | pgcc AT delorie DOT com |
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. > 2. Does aggressive inlining of code make any sense on a Pentium+ CPU? Maybe. Depends on the precise situation. jeff
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |