From: David Woodhouse <dwmw2@infradead.org>
To: dwmw2@infradead.org
Cc: linux-arch@vger.kernel.org, x86@kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/4] Use compiler intrinsics for byteswapping
Date: Tue, 4 Dec 2012 10:15:26 +0000 [thread overview]
Message-ID: <1354616130-21587-1-git-send-email-dwmw2@infradead.org> (raw)
This series of patches enables the __builtin_bswapXX() series of functions
that have been supported since GCC 4.4. It allows GCC to emit load-and-swap
or store-and-swap instructions on architectures which support that.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next reply other threads:[~2012-12-04 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 10:15 David Woodhouse [this message]
2012-12-04 10:15 ` [PATCH 1/4] byteorder: allow arch to opt to use GCC intrinsics for byteswapping David Woodhouse
2012-12-04 10:15 ` [PATCH 2/4] powerpc: enable ARCH_USE_BUILTIN_BSWAP David Woodhouse
2012-12-04 11:02 ` Stephen Rothwell
2012-12-04 14:32 ` David Woodhouse
2012-12-04 10:15 ` [PATCH 3/4] x86: " David Woodhouse
2012-12-04 10:15 ` [PATCH 4/4] x86: add CONFIG_X86_MOVBE option David Woodhouse
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=1354616130-21587-1-git-send-email-dwmw2@infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).