From: Ralf Baechle <ralf@uni-koblenz.de>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: gcc@gcc.gnu.org, Linus Torvalds <torvalds@transmeta.com>,
Andrew Morton <akpm@zip.com.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: GCC still keeps empty loops? (was: [patch 4/21] fix ARCH_HAS_PREFETCH)
Date: Mon, 12 Aug 2002 15:15:00 -0000 [thread overview]
Message-ID: <20020812094548.A22879@bacchus.dhis.org> (raw)
In-Reply-To: <20020811210718.B3206@kushida.apsleyroad.org>
On Sun, Aug 11, 2002 at 09:07:18PM +0100, Jamie Lokier wrote:
> Unbelievably, 3.1 doesn't remove empty loops either.
> I think there's a case for a compiler flag, `-fremove-empty-loops'.
Indeed ... It's sad having to scatter ifdefs over the code just because
gcc lacks this optimization ...
Ralf
prev parent reply other threads:[~2002-08-12 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D56B13A.D3F741D1@zip.com.au>
[not found] ` <Pine.LNX.4.44.0208111203520.9930-100000@home.transmeta.com>
2002-08-11 13:07 ` Jamie Lokier
2002-08-12 15:15 ` Ralf Baechle [this message]
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=20020812094548.A22879@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=torvalds@transmeta.com \
/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).