public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/49194] Trivially stupid inlining decisions Date: Sun, 25 Mar 2012 09:57:00 -0000 [thread overview] Message-ID: <bug-49194-4-QQcXdL8B3s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49194-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49194 --- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-03-25 09:43:46 UTC --- GCC 4.7 has now shrink wrapping that should reduce effect of inlining large cold functions called once. Realistic testcases where we still kill code quality would be welcome. I tested patch to disable inlining once for cold calls, but it does not help in general. What happens is that we stop inlining constructors/destructors/initialization loops that eventually kills code quality of some benchmarks since known values are no longer propagated. I will do more tunning of this for 4.8. Honza
prev parent reply other threads:[~2012-03-25 9:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-27 15:32 [Bug other/49194] New: " torvalds@linux-foundation.org 2011-05-27 16:12 ` [Bug other/49194] " jakub at gcc dot gnu.org 2011-05-27 16:15 ` matz at gcc dot gnu.org 2011-05-27 16:20 ` hubicka at ucw dot cz 2011-05-27 16:25 ` hubicka at gcc dot gnu.org 2011-05-27 16:32 ` jakub at gcc dot gnu.org 2011-05-27 16:45 ` torvalds@linux-foundation.org 2011-05-27 18:52 ` hubicka at ucw dot cz 2012-03-25 9:57 ` hubicka at gcc dot gnu.org [this message]
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-49194-4-QQcXdL8B3s@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).