From: jason.wessel@windriver.com (Jason Wessel)
Subject: [ltt-dev] [URCU PATCH] Update the README to change armv7l to arm
Date: Thu, 24 Feb 2011 07:00:10 -0600 [thread overview]
Message-ID: <1298552410-32395-1-git-send-email-jason.wessel@windriver.com> (raw)
ARM v5 and ARM v6 are known to work using compiler barriers.
Signed-off-by: Jason Wessel <jason.wessel at windriver.com>
---
README | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/README b/README
index 796b9cf..ae77189 100644
--- a/README
+++ b/README
@@ -25,10 +25,10 @@ ARCHITECTURES SUPPORTED
-----------------------
Currently, x86 (i386, i486, i586, i686), x86 64-bit, PowerPC 32/64, S390, S390x
-ARMv7l, Alpha, ia64 and Sparcv9 32/64 are supported. Only tested on Linux so
+ARM, Alpha, ia64 and Sparcv9 32/64 are supported. Only tested on Linux so
far, but should theoretically work on other operating systems.
-ARMv7l depends on running a Linux kernel 2.6.15 or better.
+ARM depends on running a Linux kernel 2.6.15 or better.
The gcc compiler versions 3.3, 3.4, 4.0, 4.1, 4.2, 4.3, 4.4 and 4.5 are
supported, with the following exceptions:
@@ -38,7 +38,7 @@ supported, with the following exceptions:
therefore not compatible with liburcu on x86 32-bit (i386, i486, i586, i686).
The problem has been reported to the gcc community:
http://www.mail-archive.com/gcc-bugs at gcc.gnu.org/msg281255.html
-- Alpha, ia64 and ARMv7l architectures depend on 4.x gcc with atomic builtins
+- Alpha, ia64 and ARM architectures depend on 4.x gcc with atomic builtins
support.
--
1.6.6.2
reply other threads:[~2011-02-24 13:00 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=1298552410-32395-1-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
/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