Force build failure on unknown architectures
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Fri, 18 Jun 2010 16:26:20 +0000 (12:26 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Fri, 18 Jun 2010 16:26:20 +0000 (12:26 -0400)
commitc53cf27f54bfb914e874ddb82a54653b6ccee276
treefd3c93cd6517aa0e8e7452761ca6d40dc8a56d21
parentfdbddd0b309449efb4db1e70e88bb5c65963b478
Force build failure on unknown architectures

Create urcu/arch_unknown.h and urcu/uatomic_arch_unknown.h, which
contain only #error statements and explanatory comments.  This forces
build failures on unrecognized architectures in preference to trying
to guess at what operations might be safe on such architectures.

One other semi-feasible alternative is to use hashed arrays of locks
that are acquired with signals disabled.  However, this seems a bit
too ornate, especially for architectures for which the gcc __sync_
primitives work correctly.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
configure.ac
urcu/arch_unknown.h [new file with mode: 0644]
urcu/uatomic_arch_unknown.h [new file with mode: 0644]
This page took 0.024424 seconds and 4 git commands to generate.