X-Git-Url: https://git.liburcu.org/?p=urcu.git;a=blobdiff_plain;f=README;h=796b9cfcd4dbad1d87775b22e53559dcdf7df7ed;hp=b3839e1a614a134c4960cc96824cefca83078d69;hb=eaf2c3f4b9041d2a6a85d7f9e56f6014603367d4;hpb=fdf01eeda9f634a32db3fc90cd342da08d7a259d

diff --git a/README b/README
index b3839e1..796b9cf 100644
--- a/README
+++ b/README
@@ -25,8 +25,22 @@ ARCHITECTURES SUPPORTED
 -----------------------
 
 Currently, x86 (i386, i486, i586, i686), x86 64-bit, PowerPC 32/64, S390, S390x
-and Sparcv9 32/64 are supported. Only tested on Linux so far, but should
-theoretically work on other operating systems.
+ARMv7l, 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.
+
+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:
+
+- gcc 3.3 and 3.4 have a bug that prevents them from generating volatile
+  accesses to offsets in a TLS structure on 32-bit x86. These versions are
+  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@gcc.gnu.org/msg281255.html
+- Alpha, ia64 and ARMv7l architectures depend on 4.x gcc with atomic builtins
+  support.
+
 
 QUICK START GUIDE
 -----------------
@@ -71,7 +85,8 @@ Usage of liburcu-mb
 
 Usage of liburcu-signal
 
-	* #include <urcu-signal.h>
+	* #include <urcu.h>
+	* Compile any _LGPL_SOURCE code using this library with "-DRCU_SIGNAL".
 	* Link the application with "-lurcu-signal".
 	* Version of the library that requires a signal, typically SIGUSR1. Can
 	  be overridden with -DSIGRCU by modifying Makefile.build.inc.
@@ -146,6 +161,14 @@ Being careful with signals
 	rcu_quiescent_state() calls, when threads are put offline and around
 	calls to synchronize_rcu(). Even then, we do not recommend it.
 
+Interaction with mutexes
+
+	One must be careful to do not cause deadlocks due to interaction of
+	synchronize_rcu() and RCU read-side with mutexes. If synchronize_rcu()
+	is called with a mutex held, this mutex (or any mutex which has this
+	mutex in its dependency chain) should not be acquired from within a RCU
+	read-side critical section.
+
 Usage of DEBUG_RCU
 
 	DEBUG_RCU is used to add internal debugging self-checks to the