public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/16690] [lno] Segfault in verify_dominators Date: Fri, 23 Jul 2004 14:38:00 -0000 [thread overview] Message-ID: <20040723143832.13768.qmail@sourceware.org> (raw) In-Reply-To: <20040723143035.16690.falk@debian.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-07-23 14:38 ------- What this usually means is that someone forgets to update the dominators correctly or wrongly. -- What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical Summary|Segfault in |[lno] Segfault in |verify_dominators |verify_dominators Target Milestone|--- |lno http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16690
next prev parent reply other threads:[~2004-07-23 14:38 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-23 14:30 [Bug tree-optimization/16690] New: " falk at debian dot org 2004-07-23 14:38 ` pinskia at gcc dot gnu dot org [this message] 2004-07-28 21:23 ` [Bug tree-optimization/16690] [lno] " pinskia at gcc dot gnu dot org 2004-07-29 8:51 ` cvs-commit at gcc dot gnu dot org 2004-07-29 8:56 ` rakdver at gcc dot gnu dot org 2004-07-29 9:00 ` falk at debian 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=20040723143832.13768.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).