This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC -On optimization passes: flag and doc issues


On Wed, Apr 18, 2007 at 12:16:32AM +0100, Dave Korn wrote:
>   Sorry for butting in, but I just can't follow the reasoning here.
> Unless a function is only ever used once and is inlined at the single
> callsite, or unless the prolog and epilog are several times the size of
> the function body, isn't inlining /always/ (not just "typically", but
> actually *always*) going to increase code size?

Nope.  C++ is full of tiny functions that (for example) get or set one
value of a class.  Inlining them strictly reduces code size.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]