public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58789] [4.8 Regression] "internal compiler error: Segmentation fault" with external definition
Date: Thu, 24 Oct 2013 17:22:00 -0000	[thread overview]
Message-ID: <bug-58789-4-HHYAMgMjPT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58789-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Well, IPA-CP devirtualization is required to trigger the bug but it is
a clone materialization problem.

The following line (invoked as a consequence of fold_stmt
devirtualization) in cgraph_update_edges_for_call_stmt_node causes the
bug:

      ne = cgraph_create_edge (node, cgraph_get_create_node (new_call),
                   new_stmt, count, frequency);

cgraph_get_create_node returns an inlined clone and it gets an extra
caller edge.  Verifier then complains there is an un-inlined edge to
an inlined node but the problem really is that there are two edges.

Either we need to make sure that we keep an un-inlined node for
devirtualization which cgraph_get_create_node can pick up until we are
done with materializations, ore need to backport and use
cgraph_get_create_real_symbol_node from
http://gcc.gnu.org/ml/gcc-patches/2013-03/msg00621.html


  parent reply	other threads:[~2013-10-24 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 16:03 [Bug c++/58789] New: " phe.bugzilla at gmail dot com
2013-10-18 16:05 ` [Bug c++/58789] " phe.bugzilla at gmail dot com
2013-10-18 16:05 ` phe.bugzilla at gmail dot com
2013-10-18 16:35 ` paolo.carlini at oracle dot com
2013-10-21  8:48 ` [Bug middle-end/58789] [4.8 Regression] " rguenth at gcc dot gnu.org
2013-10-24 17:22 ` jamborm at gcc dot gnu.org [this message]
2013-10-29 14:32 ` jamborm at gcc dot gnu.org
2013-10-29 14:43 ` jamborm 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-58789-4-HHYAMgMjPT@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).