Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Jun Sun <jsun@mvista.com>
Cc: Carsten Langgaard <carstenl@mips.com>, linux-mips@linux-mips.org
Subject: Re: Cache routine patch
Date: Thu, 12 Dec 2002 15:13:08 +0100	[thread overview]
Message-ID: <20021212151308.C6657@linux-mips.org> (raw)
In-Reply-To: <20021211090635.C6755@mvista.com>; from jsun@mvista.com on Wed, Dec 11, 2002 at 09:06:35AM -0800

On Wed, Dec 11, 2002 at 09:06:35AM -0800, Jun Sun wrote:

> Part of you patches fixes an off-by-one problem in flushing
> cache for a range of addresses.  I have a different version
> for that part which is a little more visually pleasing.
> 
> See attachment.

In case you were wondering why the whole loop construction is looking so
odd, take a look at the compiler output.  The loop construction I've
choosen is the only one that's producing bearable code.  Sad to see that
gcc is producing crap code from such a trivial loop ...

   Ralf

      reply	other threads:[~2002-12-12 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 10:56 Cache routine patch Carsten Langgaard
2002-12-11 17:06 ` Jun Sun
2002-12-12 14:13   ` 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=20021212151308.C6657@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=carstenl@mips.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@linux-mips.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