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 middle-end/55797] [4.8 Regression] ICE: verify_cgraph_node failed: edge has no corresponding call_stmt
Date: Wed, 23 Jan 2013 13:57:00 -0000	[thread overview]
Message-ID: <bug-55797-4-1cLdCcrHSe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55797-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> 2013-01-23 13:56:44 UTC ---
This is not really issue with early inliner confused with function not being in
SSA form.  But for aid of esra, we can do that at expense of increasing of peak
memory use - the SSA form is quite bloated just after built and early passes
gets it noticeably smaller, so we may need to schedule another DCE pass or so.

The problem here is however saving body of
file_info::~file_info() (struct file_info * const this)
{
  struct intrusive_ptr * _2;
  struct intrusive_ptr * _5;
  struct intrusive_ptr * _7;
  struct section_info * _9;

  <bb 2>:
  _2 = &this_1(D)->switched_section;
  _9 = _2->px;
  if (_9 != 0B)
    goto <bb 3>;
  else
    goto <bb 5> (<L2>);

  <bb 3>:
  section_info::~section_info (_9);

  <bb 4>:
  operator delete (_9);

<L2>:
  _5 = &this_1(D)->parent;
  intrusive_ptr<file_info>::~intrusive_ptr (_5);
  return;

<L1>:
  _7 = &this_1(D)->parent;
  intrusive_ptr<file_info>::~intrusive_ptr (_7);
  resx 1

}

The basic block <L1> in unreachable, but for some reason it is not removed
prior inlining.  save_function_body must run delete_unreachable_blocks in order
to update SSA after copying and that one gets rid of the call. It updates the
node itself, but not the clones.  I will add code to update clones. 

I suppose this is because


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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-23 11:04 [Bug middle-end/55797] New: " zsojka at seznam dot cz
2012-12-26 22:20 ` [Bug middle-end/55797] " pinskia at gcc dot gnu.org
2012-12-30 10:54 ` mpolacek at gcc dot gnu.org
2012-12-30 12:16 ` mpolacek at gcc dot gnu.org
2013-01-07 15:44 ` rguenth at gcc dot gnu.org
2013-01-08 13:51 ` rguenth at gcc dot gnu.org
2013-01-08 14:25 ` rguenth at gcc dot gnu.org
2013-01-23 13:29 ` hubicka at gcc dot gnu.org
2013-01-23 13:38 ` hubicka at gcc dot gnu.org
2013-01-23 13:49 ` jakub at gcc dot gnu.org
2013-01-23 13:57 ` hubicka at gcc dot gnu.org [this message]
2013-01-23 14:00 ` hubicka at gcc dot gnu.org
2013-01-23 14:20 ` hubicka at gcc dot gnu.org
2013-02-08 11:30 ` jakub 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-55797-4-1cLdCcrHSe@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).