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 ipa/64801] [5 Regression] kernel build failure due to ICF
Date: Thu, 29 Jan 2015 05:32:00 -0000	[thread overview]
Message-ID: <bug-64801-4-SwiSZbSUBa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64801-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64801

--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
OK, we do not inline it because creae_wrapper decides so:
Index: cgraphunit.c
===================================================================
--- cgraphunit.c        (revision 220229)
+++ cgraphunit.c        (working copy)
@@ -2427,7 +2427,6 @@ cgraph_node::create_wrapper (cgraph_node
     }

   expand_thunk (false, true);
-  e->call_stmt_cannot_inline_p = true;

   /* Inline summary set-up.  */
   analyze ();

Martin, perhaps this is leftover of some debugging? We ought to give inliner
freedom to re-duplicate the unified function body when it seems profitable
(like here)


  parent reply	other threads:[~2015-01-29  5:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 14:39 [Bug ipa/64801] New: " trippels at gcc dot gnu.org
2015-01-26 15:22 ` [Bug ipa/64801] " rguenth at gcc dot gnu.org
2015-01-26 15:50 ` marxin at gcc dot gnu.org
2015-01-27 17:31 ` hubicka at gcc dot gnu.org
2015-01-29  5:30 ` hubicka at gcc dot gnu.org
2015-01-29  5:32 ` hubicka at gcc dot gnu.org [this message]
2015-01-29  5:43 ` hubicka at gcc dot gnu.org
2015-01-29  7:43 ` hubicka at gcc dot gnu.org
2015-01-29  7:44 ` hubicka at gcc dot gnu.org

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-64801-4-SwiSZbSUBa@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: 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).