public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/97489] [11 Regression] ICE: Segmentation fault (in ana::supergraph::get_node_for_function_entry(function*) const) since r10-5950-g757bf1dff5e8cee3
Date: Mon, 19 Oct 2020 14:12:00 +0000 [thread overview]
Message-ID: <bug-97489-4-UyibG1uOp5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97489-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97489
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks; confirmed, though for me I see the ICE with
g:af66094d037793773eb8a49597866457f2f6a104, and do not see the ICE with its
predecessor; in particular the backtrace shows add_any_callbacks which I added
in that commit.
It's crashing on "__dt_comp ", finding the dtor in the vtable when building the
initial worklist, here:
96 return get_node_for_block (ENTRY_BLOCK_PTR_FOR_FN (fun));
where fun->cfg is NULL. Working on a fix.
next prev parent reply other threads:[~2020-10-19 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 10:12 [Bug analyzer/97489] New: [11 Regression] ICE: Segmentation fault (in ana::supergraph::get_node_for_function_entry(function*) const) asolokha at gmx dot com
2020-10-19 12:06 ` [Bug analyzer/97489] " rguenth at gcc dot gnu.org
2020-10-19 12:15 ` [Bug analyzer/97489] [11 Regression] ICE: Segmentation fault (in ana::supergraph::get_node_for_function_entry(function*) const) since r10-5950-g757bf1dff5e8cee3 marxin at gcc dot gnu.org
2020-10-19 14:12 ` dmalcolm at gcc dot gnu.org [this message]
2020-10-22 10:13 ` cvs-commit at gcc dot gnu.org
2020-10-22 10:32 ` dmalcolm 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-97489-4-UyibG1uOp5@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).