From: Toon Moene <toon@moene.org>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Jan Hubicka <jh@suse.cz>, gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: LTO and the inlining of functions only called once.
Date: Sat, 10 Oct 2009 12:31:00 -0000 [thread overview]
Message-ID: <4AD07BA5.2000800@moene.org> (raw)
In-Reply-To: <84fc9c000910100450w220ee337q6d6f7c53d8a67727@mail.gmail.com>
Richard Guenther wrote:
> On Sat, Oct 10, 2009 at 1:46 PM, Richard Guenther
> <richard.guenther@gmail.com> wrote:
>> On Sat, Oct 10, 2009 at 1:34 PM, Toon Moene <toon@moene.org> wrote:
[ Inlining all functions called once ]
>>> I'd like to see some fireworks, too !
>> That's not the parameter you want to tweak ;) You want
>>
>> --param large-function-growth=10000 --param large-function-insns=1000000
>> --param large-stack-frame-growth=10000 --param large-stack-frame=100000
>
> Or rather for testing the effect of inlining all functions called once
> use the following
> patch:
>
> Index: ipa-inline.c
> ===================================================================
> --- ipa-inline.c (revision 152615)
> +++ ipa-inline.c (working copy)
> @@ -1249,8 +1249,8 @@ cgraph_decide_inlining (void)
> node->callers->caller->global.size);
> }
>
> - if (cgraph_check_inline_limits (node->callers->caller, node,
> - NULL, false))
> + if (1 || cgraph_check_inline_limits (node->callers->caller, node,
> + NULL, false))
> {
> cgraph_mark_inline (node->callers);
> if (dump_file)
Going this route, thanks !
> tuning params will affect other inlining decisions as well.
Yep, I was afraid of that too, but think it is inconsequential for our code.
Thanks !
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/
Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html
next prev parent reply other threads:[~2009-10-10 12:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 11:00 Toon Moene
2009-10-10 11:34 ` Richard Guenther
2009-10-10 11:47 ` Toon Moene
2009-10-10 11:50 ` Richard Guenther
2009-10-10 12:18 ` Richard Guenther
2009-10-10 12:31 ` Toon Moene [this message]
2009-10-10 14:25 ` Toon Moene
2009-10-10 15:10 ` Richard Guenther
2009-10-10 13:40 ` Jan Hubicka
2009-10-10 15:27 ` Daniel Jacobowitz
2009-10-10 15:28 ` Jan Hubicka
2009-10-11 13:30 ` Toon Moene
2009-10-10 15:33 ` Diego Novillo
2009-10-10 17:26 ` Joseph S. Myers
2009-10-14 20:07 ` Paolo Bonzini
2009-10-10 16:40 ` Jeff Law
2009-10-10 17:16 ` Richard Guenther
2009-10-13 1:05 ` Jeff Law
2009-10-13 1:29 ` Michael Matz
2009-10-13 6:39 ` Jeff Law
2009-10-13 12:05 ` Paul Brook
2009-10-13 13:30 ` Daniel Jacobowitz
2009-10-13 15:15 ` Jeff Law
2009-10-13 18:31 ` Adam Nemet
2009-10-13 18:43 ` Toon Moene
2009-10-14 10:05 ` Richard Guenther
2009-10-14 13:48 ` Toon Moene
2009-10-14 14:04 ` Toon Moene
2009-10-14 14:43 ` Jan Hubicka
2009-10-14 16:49 ` Daniel Jacobowitz
2009-10-14 18:20 ` Toon Moene
2009-10-14 18:58 ` Paolo Bonzini
2009-10-14 19:09 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD07BA5.2000800@moene.org \
--to=toon@moene.org \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=richard.guenther@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).