This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][3.4] Fix PR15366, -fno-inline-functions is ignored for static functions
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 1 Sep 2005 10:11:01 +0200
- Subject: Re: [PATCH][3.4] Fix PR15366, -fno-inline-functions is ignored for static functions
- References: <Pine.LNX.4.58.0508311510400.21309@wotan.suse.de> <4315B0EE.1000907@lu.unisi.ch>
On 8/31/05, Paolo Bonzini <paolo.bonzini@lu.unisi.ch> wrote:
>
> > + @item -finline-functions-called-once
> > + @opindex finline-functions-called-once
> > + Integrate functions called once into their callers. The compiler
> > + heuristically decides which functions are simple enough to be worth
> > + integrating in this way.
>
> This doc seems a bit incomplet and/or incorrekt... I think something
> simpler, like
>
> Integrate functions called once into their callers, even if not marked
> as @code{inline}.
I simplified it to:
Consider all @code{static} functions called once for inlining into their
caller even if they are not marked @code{inline}. If a call to a given
function is integrated, then the function is not output as assembler code
in its own right.
The "... in its own right" sounds weird to me, but I copied it from
inline-functions
description - it may be a valid idiom anyway(?)
Better?
Thanks,
Richard.