public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55823] [4.8 Regression] ice in inline_call, at ipa-inline-transform.c:270
Date: Tue, 01 Jan 2013 23:32:00 -0000	[thread overview]
Message-ID: <bug-55823-4-4414wfuOsD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55823-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55823

--- Comment #4 from Jan Hubicka <hubicka at ucw dot cz> 2013-01-01 23:32:27 UTC ---
This is the usual problem of devirt benefit predicting more devirtualization
than inline-transform actually doing.  This time it seems to be related to fact
that we first clone the function and propagate &m_paintdc but somehow fail to
recognize the devirtualizatoin oppurtunities again...

Honza


  parent reply	other threads:[~2013-01-01 23:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 11:57 [Bug c++/55823] New: " dcb314 at hotmail dot com
2012-12-31 10:34 ` [Bug c++/55823] [4.8 Regression] " pinskia at gcc dot gnu.org
2012-12-31 11:57 ` [Bug tree-optimization/55823] " pinskia at gcc dot gnu.org
2013-01-01 23:32   ` Jan Hubicka
2012-12-31 12:01 ` pinskia at gcc dot gnu.org
2013-01-01 23:32 ` hubicka at ucw dot cz [this message]
2013-01-02  0:10   ` Jan Hubicka
2013-01-02  0:11 ` hubicka at ucw dot cz
2013-01-02 10:33 ` rguenth at gcc dot gnu.org
2013-01-03 16:23 ` hubicka at gcc dot gnu.org
2013-01-03 16:26 ` hubicka at gcc dot gnu.org
2013-01-08 20:23 ` hubicka at gcc dot gnu.org
2013-01-09  9:07 ` hubicka at gcc dot gnu.org
2013-01-09  9:33 ` rguenth 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-55823-4-4414wfuOsD@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).