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 tree-optimization/45178] CDDCE doesn't eliminate conditional code in infinite loop
Date: Wed, 04 Aug 2010 13:21:00 -0000 [thread overview]
Message-ID: <20100804132134.14414.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45178-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from rguenth at gcc dot gnu dot org 2010-08-04 13:21 -------
(In reply to comment #1)
> Subject: Re: New: CDDCE doesn't eliminate
> conditional code in infinite loop
>
> Hmm, so the problem is that we produce two alternating loops and both with
> unknown number of iterations?
> We might teach loop discovery to preffer single infinite loop over alternation
> I guess.
Yeah, that might help.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2010-08-04 13:21:34
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45178
next prev parent reply other threads:[~2010-08-04 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 9:46 [Bug tree-optimization/45178] New: " rguenth at gcc dot gnu dot org
2010-08-04 13:05 ` [Bug tree-optimization/45178] " hubicka at ucw dot cz
2010-08-04 13:21 ` rguenth at gcc dot gnu dot org [this message]
[not found] <bug-45178-4@http.gcc.gnu.org/bugzilla/>
2021-08-26 12:02 ` rguenth at gcc dot gnu.org
2021-08-26 14:35 ` hubicka at ucw dot cz
2021-08-27 7:51 ` cvs-commit at gcc dot gnu.org
2021-08-27 7:52 ` rguenth at gcc dot gnu.org
2022-02-17 11:26 ` cvs-commit 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=20100804132134.14414.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).