This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/35042] Documentation for -finline-limit is incorrect
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Jan 2008 16:22:26 -0000
- Subject: [Bug other/35042] Documentation for -finline-limit is incorrect
- References: <bug-35042-15713@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from rguenther at suse dot de 2008-01-31 16:22 -------
Subject: Re: Documentation for -finline-limit is incorrect
On Thu, 31 Jan 2008, ddenisen at altera dot com wrote:
> ------- Comment #4 from ddenisen at altera dot com 2008-01-31 16:12 -------
> > @emph{Note:} there may be no value to @option{-finline-limit} that results
> > in default behavior.
>
> That's also not user-friendly. When it is changed, it is not clear what is
> "more aggressive" inlining and what is not.
>
> Why don't you make max-inline-insns-single = 5*n/2 and max-inline-insns-auto =
> n/2? This way, we have a default that is consistent with current settings and
> setting -finline-limit=180 gives you exactly the default.
Actually this would be a change in behavior (the current behavior is at
least present since gcc 3.3). We can retain a hint at in which range
the default value lies for functions explicitly marked as inline (around
900).
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35042