public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stevenb at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/17358] [3.5 Regression] infinite loop due to incorrect updating of the dominator tree
Date: Thu, 09 Sep 2004 21:52:00 -0000 [thread overview]
Message-ID: <20040909215252.3243.qmail@sourceware.org> (raw)
In-Reply-To: <20040908194538.17358.steven@gcc.gnu.org>
------- Additional Comments From stevenb at suse dot de 2004-09-09 21:52 -------
Subject: Re: [3.5 Regression] infinite loop due to incorrect updating of the dominator tree
On Thursday 09 September 2004 18:26, belyshev at lubercy dot com wrote:
> This bug seems to be fixed now (after 13:00..15:00 2004-09-09 UTC).
Did you verify this with the original test case? The
shorter test case you provide may be fixed by some lucky
incident. For example, "void foo() { for (;;); } also
went into an infinite loop (maybe it still does) but that
was an unrelated bug.
Gr.
Steven
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17358
next prev parent reply other threads:[~2004-09-09 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 19:45 [Bug tree-optimization/17358] New: " steven at gcc dot gnu dot org
2004-09-08 19:47 ` [Bug tree-optimization/17358] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-09-08 19:52 ` pinskia at gcc dot gnu dot org
2004-09-09 16:26 ` belyshev at lubercy dot com
2004-09-09 21:52 ` stevenb at suse dot de [this message]
2004-09-09 23:33 ` steven at gcc dot gnu dot org
2004-09-09 23:34 ` steven at gcc dot gnu dot org
2004-09-10 0:06 ` belyshev at lubercy dot com
2004-09-10 8:12 ` steven at gcc dot gnu dot org
2004-09-12 18:47 ` pinskia at gcc dot gnu dot org
2004-09-14 11:38 ` [Bug tree-optimization/17358] [4.0 " giovannibajo at libero dot it
2004-09-14 11:39 ` giovannibajo at libero dot it
2004-09-14 11:41 ` steven 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=20040909215252.3243.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: 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).