public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: David Lang <david.lang@digitalinsight.com>
Cc: Willy Tarreau <willy@w.ods.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 4/21] fix ARCH_HAS_PREFETCH
Date: Thu, 15 Aug 2002 08:44:04 +0200	[thread overview]
Message-ID: <20020815064404.GC7445@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141551020.14879-100000@dlang.diginsite.com>

On Wed, Aug 14, 2002 at 03:53:15PM -0700, David Lang wrote:
> why are you useing loops for delays in the first place? it's a solution
> that will fail as clock speeds keep improving (if for no other reason then
> your loop counter will end up needing to be a larger int to achieve the
> desired delay!!)
> 
> 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.

I'm NEVER using loops for delays, I find this awful and always a waste of
time. But sometimes, you want to benchmark some algorithms, and the compiler
makes this difficult by eliminating things it thinks are useless. I once had
this problem when comparing several linked lists algorithms, for example.

Moreover, some people complain about the fact that gcc doesn't optimize
everything because of people using loops for delays. If we provide convenient
ways to help the user tell gcc when not to optimize, gcc could optimize
everything possible by default.

Cheers,
Willy


  parent reply	other threads:[~2002-08-15  6:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-11  7:38 [patch 4/21] fix ARCH_HAS_PREFETCH 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
2002-08-15  6:44                 ` Willy Tarreau [this message]
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=20020815064404.GC7445@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=david.lang@digitalinsight.com \
    --cc=hpa@zytor.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