From: Harvey Harrison <harvey.harrison@gmail.com>
To: Chris Zankel <chris@zankel.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Bob Wilson <bwilson@tensilica.com>
Subject: Re: [PATCH 3/4] xtensa: Change unaligned access to use packed struct implementation
Date: Thu, 09 Oct 2008 22:39:47 -0700 [thread overview]
Message-ID: <1223617187.8991.1.camel@brick> (raw)
In-Reply-To: <48EEE546.9070405@zankel.net>
On Thu, 2008-10-09 at 22:16 -0700, Chris Zankel wrote:
> Hi Harvey,
>
> Please allow me a couple of days to look into it. I don't know the
> historic reasons why the memmove variant was chosen.
>
> Thanks,
> -Chris
>
Sure, from the comments in the original version, it looks like it was done
this way to avoid __builtin_memcpy from being generated. But maybe there was another
reason?
Harvey
prev parent reply other threads:[~2008-10-10 5:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 6:38 [PATCH 3/4] xtensa: Change unaligned access to use packed struct implementation Harvey Harrison
2008-10-10 5:16 ` Chris Zankel
2008-10-10 5:39 ` Harvey Harrison [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=1223617187.8991.1.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bwilson@tensilica.com \
--cc=chris@zankel.net \
--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