From 876d39cd86446ba0fe79ad20f1d261e5d85d659b Mon Sep 17 00:00:00 2001 From: Rickard Green Date: Mon, 8 Jul 2013 17:20:21 +0200 Subject: Refuse to build SMP runtime by default without native atomics Build with fallback can be enabled by passing the `configure` command line argument `--disable-smp-require-native-atomics` --- HOWTO/INSTALL.md | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'HOWTO') diff --git a/HOWTO/INSTALL.md b/HOWTO/INSTALL.md index 8051bc4393..fa1b9d2e89 100644 --- a/HOWTO/INSTALL.md +++ b/HOWTO/INSTALL.md @@ -288,6 +288,14 @@ Some of the available `configure` options are: implementation available, you typically want to try using the `libatomic_ops` library. It can be downloaded from . +* `--disable-smp-require-native-atomics` - By default `configure` will + fail if an SMP runtime system is about to be built, and no implementation + for native atomic memory accesses can be found. If this happens, you are + encouraged to find a native atomic implementation that can be used, e.g., + using `libatomic_ops`, but by passing `--disable-smp-require-native-atomics` + you can build using a fallback implementation based on mutexes or spinlocks. + Performance of the SMP runtime system will however suffer immensely without + an implementation for native atomic memory accesses. If you or your system has special requirements please read the `Makefile` for additional configuration information. -- cgit v1.2.3