public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62071] [4.10 Regression] ICE: in before_dom_children, at tree-ssa-pre.c:4411
Date: Thu, 14 Aug 2014 19:40:00 -0000	[thread overview]
Message-ID: <bug-62071-4-0ZZeNJUAgK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62071-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jason Merrill <jason at redhat dot com> ---
On 08/14/2014 02:10 PM, Jan Hubicka wrote:
> I wonder what we should do with both external and comdat here.  Jason, can we devirtualize?

No, we're setting comdat now to avoid devirtualization, because we can't 
be confident that we'll be able to refer to the definition where it gets 
emitted.

> The constructor is keyed to other compilation unit here, but we are provided with a body
> that we will never use (modulo the tree-ssa-pre bug that brings the reference into code).

Hmm, we might consider overriding DECL_EXTERNAL so that there's a 
definition available for devirtualization.

Jason


  parent reply	other threads:[~2014-08-14 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 20:38 [Bug tree-optimization/62071] New: " trippels at gcc dot gnu.org
2014-08-10  6:23 ` [Bug tree-optimization/62071] " trippels at gcc dot gnu.org
2014-08-14 18:28 ` trippels at gcc dot gnu.org
2014-08-14 19:40 ` jason at redhat dot com [this message]
2014-08-14 23:14 ` hubicka at ucw dot cz
2014-08-15 17:37 ` jason at redhat dot com
2014-08-15 21:20 ` hubicka at ucw dot cz
2014-08-17 15:57 ` hubicka at ucw dot cz

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-62071-4-0ZZeNJUAgK@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).