atomic_compare_exchange_weak atomic_exchange atomic_fetch_add atomic_fetch_add_conditional atomic_fetch_and atomic_fetch_max atomic_fetch_or atomic_fetch_sub atomic_fetch_xor atomic_flag_clear atomic_flag_clear_explicit atomic_flag_lock atomic_flag_test_and_set atomic_flag_test_and_set_explicit atomic_flag_trylock atomic_flag_unlock atomic_init atomic_is_lock_free atomic_load atomic_store P99_CRITICAL P99_FIFO P99_FIFO_APPEND P99_FIFO_CLEAR P99_FIFO_DECLARE P99_FIFO_INITIALIZER P99_FIFO_POP P99_FIFO_TABULATE P99_LIFO P99_LIFO_CLEAR P99_LIFO_DECLARE P99_LIFO_INITIALIZER P99_LIFO_POP P99_LIFO_PUSH P99_LIFO_TABULATE P99_LIFO_TOP P99_SPIN_EXCLUDE

#define P99_CRITICAL Value: P00_BLK_START \ P00_BLK_DECL_STATIC(atomic_flag, P99_LINEID(crit), ATOMIC_FLAG_INIT) \ P99_SPIN_EXCLUDE(P99_LINEID(crit)) Protect the following block or statement as a critical section of the program. Internally this uses a static atomic_flag as a spinlock, so this is an active wait. Warning: Such a section should only contain a handful of statements. Such a section should not contain preliminary exits such as goto, break, return, longjmp, or P99_UNWIND etc. P99_CRITICAL { // do some operations on a fragile resource here } Such a critical section is only protected against threads that try to enter this same critical section. Threads may well simultaneously be in different critical sections. Remarks: Don't use this if you just want to protect e.g a counter that is shared between different threads. _Atomic and the operations on atomic variables are more appropriate for that. See also: P99_SPIN_EXCLUDE to protect several critical sections against each other. P99_MUTUAL_EXCLUDE that is more suited for larger sections. Warning: Restrictions on preliminary exits from the dependent block or statement apply. See also: P99_PROTECTED_BLOCK P99_GUARDED_BLOCK Definition at line 1372 of file p99_atomic.h.