public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/54966] New: Does LTO requires a larger inline-unit-growth? Date: Thu, 18 Oct 2012 06:29:00 -0000 [thread overview] Message-ID: <bug-54966-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54966 Bug #: 54966 Summary: Does LTO requires a larger inline-unit-growth? Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: vincenzo.innocente@cern.ch experimenting with our large application I'm under the impression that in order to get the same level of inlining with lto I need to increase --param inline-unit-growth to at least 50 (my understanding is that the default is 30). Is this something expected / already observed? Do you have any plan to retune heuristics for lto? It is quite critical with some meta-template "expression expansion" code
next reply other threads:[~2012-10-18 6:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-18 6:29 vincenzo.innocente at cern dot ch [this message] 2012-10-18 7:47 ` [Bug lto/54966] " dominiq at lps dot ens.fr 2012-10-18 9:44 ` rguenth at gcc dot gnu.org 2012-10-19 8:37 ` vincenzo.innocente at cern dot ch 2012-10-23 13:59 ` hubicka at ucw dot cz 2012-10-23 14:02 ` rguenther at suse dot de 2012-10-23 14:13 ` hubicka at ucw dot cz 2012-11-08 16:44 ` hubicka at gcc dot gnu.org 2012-11-09 6:39 ` vincenzo.innocente at cern dot ch 2012-11-09 6:52 ` vincenzo.innocente at cern dot ch 2012-11-09 11:33 ` vincenzo.innocente at cern dot ch 2012-11-12 13:20 ` vincenzo.innocente at cern dot ch
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=bug-54966-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).