All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: [4/3] fix initrd memcpy
Date: Tue, 21 Dec 2004 06:39:01 +0000	[thread overview]
Message-ID: <20041221063901.GF771@holomorphy.com> (raw)
In-Reply-To: <20041221045627.GC771@holomorphy.com>

On Mon, 20 Dec 2004 20:56:27 -0800 William Lee Irwin III wrote:
>> The latter hunk of the forwarded patch has already been applied, so
>> please apply the patch as it appears in the un-forwarded part. I've
>> taken some liberties in adding the Acked/Signed-off lines in what I
>> hope is an agreeable way.
>
On Mon, Dec 20, 2004 at 10:28:38PM -0800, David S. Miller wrote:
> For this one it may be advisable to kill this silly attempt
> to optimize constant count memcpy()'s.  GCC knows very well
> when to do a __builtin_memcpy() expansion vs. a real memcpy
> call.
> All the memcpy --> __memcpy is doing is making it so that the
> memcpy assembler doesn't need to retain and return the original
> destination pointer argument.
> Sparc64 was doing silly stuff like this too, and it simplified
> things a lot to just kill all of these macroized optimizations.
> I did that as follows:

This looks tremendously cleaner. I'll look for an ack to see if there
are actively participating users lingering about with toolchains that
do something unintelligible out of paranoia and then send an analogue
of this upstream.


-- wli

  parent reply	other threads:[~2004-12-21  6:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  4:56 [4/3] fix initrd memcpy William Lee Irwin III
2004-12-21  6:28 ` David S. Miller
2004-12-21  6:39 ` William Lee Irwin III [this message]
2004-12-21  7:00 ` William Lee Irwin III
2004-12-21  7:58 ` David S. Miller
2004-12-21  8:28 ` William Lee Irwin III

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=20041221063901.GF771@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.