public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/20225] [4.0/4.1 regression] ICE during GC Date: Thu, 10 Mar 2005 13:37:00 -0000 [thread overview] Message-ID: <20050310133740.19678.qmail@sourceware.org> (raw) In-Reply-To: <20050226232106.20225.schwab@suse.de> ------- Additional Comments From rth at gcc dot gnu dot org 2005-03-10 13:37 ------- The problem appears to be unrelated to the referenced patch. Debugging shows that we have a node that has been removed from the cgraph_nodes list. Because the node is not on the cgraph_nodes list, the node->prev->next == node invariant does not hold, and so the code generated by the chain_next/chain_prev GTY annotations segfaults. The node is still reachable from another node's next_needed, which seems like the real bug. Honza agreed to work on the problem on IRC. The easiest way to show the problem is to manually add if (x != NULL && x != (void *)1 && x->previous == NULL && x != cgraph_nodes) abort (); to gt_ggc_mx_cgraph_node. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rth at gcc dot gnu dot org |jh at suse dot cz http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20225
next prev parent reply other threads:[~2005-03-10 13:37 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-27 10:47 [Bug c++/20225] New: " schwab at suse dot de 2005-02-27 11:16 ` [Bug c++/20225] " schwab at suse dot de 2005-02-27 11:25 ` [Bug middle-end/20225] " pinskia at gcc dot gnu dot org 2005-02-27 12:53 ` pinskia at gcc dot gnu dot org 2005-02-27 13:54 ` pinskia at gcc dot gnu dot org 2005-02-27 21:37 ` schwab at suse dot de 2005-02-27 22:05 ` schwab at suse dot de 2005-03-03 12:56 ` schwab at suse dot de 2005-03-04 18:09 ` rth at gcc dot gnu dot org 2005-03-10 13:37 ` rth at gcc dot gnu dot org [this message] 2005-03-10 15:15 ` rth at gcc dot gnu dot org 2005-03-13 5:20 ` pinskia at gcc dot gnu dot org 2005-03-18 14:57 ` cvs-commit at gcc dot gnu dot org 2005-03-18 18:16 ` cvs-commit at gcc dot gnu dot org 2005-03-24 17:44 ` mmitchel at gcc dot gnu dot org 2005-03-25 11:05 ` jakub at gcc dot gnu dot org 2005-03-27 19:35 ` hubicka at gcc dot gnu dot org 2005-04-01 13:11 ` pinskia at gcc dot gnu dot 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=20050310133740.19678.qmail@sourceware.org \ --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: linkBe 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).