-----------------------
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
-----------------
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.
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
projects / urcu.git / blobdiff