From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: David Lang <david.lang@digitalinsight.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 4/21] fix ARCH_HAS_PREFETCH
Date: Thu, 15 Aug 2002 00:31:19 +0100 [thread overview]
Message-ID: <20020815003119.A27436@kushida.apsleyroad.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141551020.14879-100000@dlang.diginsite.com>; from david.lang@digitalinsight.com on Wed, Aug 14, 2002 at 03:53:15PM -0700
David Lang wrote:
> rather then debating how to convince gcc how to not optimize them away and
> messing up the timing we should be talking about how to eliminate such
> loops in the first place.
You misunderstand. We _do_ want gcc to optimize away empty loops.
-- Jamie
next prev parent reply other threads:[~2002-08-14 23:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 7:38 Andrew Morton
2002-08-11 19:49 ` Alan Cox
2002-08-11 18:47 ` Andrew Morton
2002-08-11 18:46 ` Larry McVoy
2002-08-11 19:06 ` Linus Torvalds
2002-08-11 20:07 ` GCC still keeps empty loops? (was: [patch 4/21] fix ARCH_HAS_PREFETCH) Jamie Lokier
2002-08-12 7:45 ` Ralf Baechle
2002-08-13 21:42 ` [patch 4/21] fix ARCH_HAS_PREFETCH Adrian Bunk
2002-08-13 22:12 ` H. Peter Anvin
2002-08-13 22:22 ` Adrian Bunk
2002-08-13 22:42 ` H. Peter Anvin
2002-08-14 17:40 ` Rogier Wolff
2002-08-14 19:41 ` H. Peter Anvin
2002-08-14 19:57 ` Jamie Lokier
2002-08-14 22:03 ` Daniel Jacobowitz
2002-08-14 20:45 ` Willy Tarreau
2002-08-14 20:58 ` H. Peter Anvin
2002-08-14 21:11 ` Willy Tarreau
2002-08-14 21:13 ` H. Peter Anvin
2002-08-15 1:23 ` Alan Cox
2002-08-15 1:28 ` H. Peter Anvin
2002-08-15 1:37 ` Alan Cox
2002-08-14 22:53 ` David Lang
2002-08-14 23:31 ` Jamie Lokier [this message]
2002-08-15 6:44 ` Willy Tarreau
2002-08-15 6:55 ` H. Peter Anvin
[not found] <3D56147E.15E7A98@zip.com.au.suse.lists.linux.kernel>
2002-08-11 9:53 ` Andi Kleen
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=20020815003119.A27436@kushida.apsleyroad.org \
--to=lk@tantalophile.demon.co.uk \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®