From: David Woodhouse <dwmw2@infradead.org>
To: torvalds@linux-foundation.org
Cc: linux-arch@vger.kernel.org
Subject: [GIT *] Preparatory patch for using GCC intrinsics for byteswapping
Date: Wed, 19 Dec 2012 13:15:36 +0000 [thread overview]
Message-ID: <1355922936.18919.69.camel@shinybook.infradead.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
Linus, please pull from
git://git.infradead.org/users/dwmw2/byteswap.git byteswap-for-linus-20121219
This single patch is effectively a no-op for now. It enables architectures
to opt in to using GCC's __builtin_bswapXX() intrinsics for byteswapping,
and if we merge this now then the architecture maintainers can enable it
for their arch during the next cycle without dependency issues.
It's worth making it a par-arch opt-in, because although in *theory* the
compiler should never do worse than hand-coded assembler (and of course
it also ought to do a lot better on platforms like Atom and PowerPC which
have load-and-swap or store-and-swap instructions), that isn't always the
case. See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46453 for example.
David Woodhouse (1):
byteorder: allow arch to opt to use GCC intrinsics for byteswapping
arch/Kconfig | 19 +++++++++++++++++++
include/linux/compiler-gcc4.h | 10 ++++++++++
include/linux/compiler-intel.h | 7 +++++++
include/uapi/linux/swab.h | 12 +++++++++---
4 files changed, 45 insertions(+), 3 deletions(-)
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
reply other threads:[~2012-12-19 13:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1355922936.18919.69.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).