public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/29254] [4.2 Regression] verify_cgraph_node failed (inlined_to pointer is set but no predecessors found) Date: Mon, 09 Oct 2006 12:25:00 -0000 [thread overview] Message-ID: <20061009122458.26402.qmail@sourceware.org> (raw) In-Reply-To: <bug-29254-12387@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from rguenth at gcc dot gnu dot org 2006-10-09 12:24 ------- The minimal fix is to not verify_cgraph_node if errorcount || sorrycount. Bailing out earlier has interesting side-effects it seems. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |rguenth at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2006-09-28 10:55:21 |2006-10-09 12:24:56 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29254
next prev parent reply other threads:[~2006-10-09 12:25 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-27 16:59 [Bug tree-optimization/29254] New: " tbm at cyrius dot com 2006-09-27 17:01 ` [Bug tree-optimization/29254] " pinskia at gcc dot gnu dot org 2006-09-27 18:12 ` pinskia at gcc dot gnu dot org 2006-09-27 18:34 ` pinskia at gcc dot gnu dot org 2006-09-27 21:31 ` lopezibanez at gmail dot com 2006-09-28 10:55 ` rguenth at gcc dot gnu dot org 2006-09-29 0:37 ` lopezibanez at gmail dot com 2006-09-29 0:53 ` lopezibanez at gmail dot com 2006-10-01 23:03 ` mmitchel at gcc dot gnu dot org 2006-10-04 20:21 ` lopezibanez at gmail dot com 2006-10-05 5:08 ` [Bug middle-end/29254] " pinskia at gcc dot gnu dot org 2006-10-09 12:25 ` rguenth at gcc dot gnu dot org [this message] 2006-10-09 16:11 ` rguenth at gcc dot gnu dot org 2006-10-09 16:11 ` rguenth at gcc dot gnu dot org 2006-10-15 15:31 ` 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=20061009122458.26402.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).