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/17640] empty loop not removed after optimization
Date: Wed, 11 May 2005 13:14:00 -0000 [thread overview]
Message-ID: <20050511131410.24483.qmail@sourceware.org> (raw)
In-Reply-To: <20040923211344.17640.wouter.vermaelen@pi.be>
------- Additional Comments From stevenb at suse dot de 2005-05-11 13:14 -------
Subject: Re: empty loop not removed after optimization
On Wednesday 11 May 2005 14:58, giovannibajo at libero dot it wrote:
> ------- Additional Comments From giovannibajo at libero dot it 2005-05-11
> 12:58 ------- This is a most-wanted feature. Are there hope to see a patch
> landing for 4.1? Can the patch that Zdenek posted be updated for 4.1? Even
> if it's gross is surely better than nothing...
nothing is better than gross.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17640
next prev parent reply other threads:[~2005-05-11 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 21:13 [Bug c/17640] New: " wouter dot vermaelen at pi dot be
2004-09-23 23:01 ` [Bug c/17640] " pinskia at gcc dot gnu dot org
2004-09-23 23:05 ` [Bug tree-optimization/17640] " pinskia at gcc dot gnu dot org
2004-12-24 2:26 ` pinskia at gcc dot gnu dot org
2005-01-28 14:26 ` rguenth at tat dot physik dot uni-tuebingen dot de
2005-01-28 15:18 ` steven at gcc dot gnu dot org
2005-05-11 12:58 ` giovannibajo at libero dot it
2005-05-11 13:00 ` pinskia at gcc dot gnu dot org
2005-05-11 13:02 ` rguenth at gcc dot gnu dot org
2005-05-11 13:14 ` stevenb at suse dot de [this message]
2005-05-11 13:16 ` steven at gcc dot gnu dot org
2005-06-30 21:48 ` steven at gcc dot gnu dot org
2005-07-12 0:01 ` 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=20050511131410.24483.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).