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 middle-end/55078] [4.8 Regression] FAIL: g++.dg/torture/pr46154.C
Date: Sat, 27 Oct 2012 09:18:00 -0000	[thread overview]
Message-ID: <bug-55078-4-Pz7njlEyj0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55078-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #4 from Jan Hubicka <hubicka at ucw dot cz> 2012-10-27 09:18:09 UTC ---
Actually, this seems like another latent problem in devirtualization.  We
assert because estimate_edge_devirt_benefit works out we can devirtualize the
call, but try_make_edge_direct_virtual_call used in inline transform does not.

It seems because estimate_edge_devirt_benefit uses the type information
provided by ipa-cp that is cowardly ignored by
try_make_edge_direct_virtual_call.  Martin, can you take a look?


Honza


  parent reply	other threads:[~2012-10-27  9:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26  3:57 [Bug middle-end/55078] New: " hjl.tools at gmail dot com
2012-10-26 10:10 ` [Bug middle-end/55078] " rguenth at gcc dot gnu.org
2012-10-26 20:30 ` hp at gcc dot gnu.org
2012-10-26 21:23 ` dominiq at lps dot ens.fr
2012-10-26 21:23 ` dominiq at lps dot ens.fr
2012-10-27  7:05 ` hubicka at ucw dot cz
2012-10-27  9:18 ` hubicka at ucw dot cz [this message]
2012-10-27  9:23 ` hubicka at gcc dot gnu.org
2012-10-29 16:15 ` jamborm at gcc dot gnu.org
2012-11-01 12:43 ` hubicka at gcc dot gnu.org
2012-11-16 17:33 ` hubicka at gcc dot gnu.org
2012-12-07 12:07 ` rguenth at gcc dot gnu.org
2012-12-07 13:06 ` jamborm at gcc dot gnu.org
2012-12-07 13:08 ` jamborm at gcc dot gnu.org
2012-12-09  0:22 ` pinskia 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-55078-4-Pz7njlEyj0@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).