added info if atomic ops are available to rsyslogd -v output

This commit is contained in:
Rainer Gerhards 2009-01-30 15:40:53 +01:00
parent b54797da05
commit 25245cc682
2 changed files with 12 additions and 0 deletions

View File

@ -46,6 +46,13 @@
# define ATOMIC_FETCH_32BIT(data) ((unsigned) __sync_fetch_and_and(&(data), 0xffffffff))
# define ATOMIC_STORE_1_TO_32BIT(data) __sync_lock_test_and_set(&(data), 1)
#else
/* note that we gained parctical proof that theoretical problems DO occur
* if we do not properly address them. See this blog post for details:
* http://blog.gerhards.net/2009/01/rsyslog-data-race-analysis.html
* The bottom line is that if there are no atomics available, we should NOT
* simply go ahead and do without them - use mutexes or other things. The
* code needs to be checked against all those cases. -- rgerhards, 2009-01-30
*/
# warning "atomic builtins not available, using nul operations - rsyslogd will probably be racy!"
# define ATOMIC_INC(data) (++(data))
# define ATOMIC_DEC_AND_FETCH(data) (--(data))

View File

@ -2792,6 +2792,11 @@ static void printVersion(void)
#else
printf("\tFEATURE_DEBUG (debug build, slow code):\tNo\n");
#endif
#ifdef HAVE_ATOMIC_BUILTINS
printf("\tAtomic operations supported:\t\tYes\n");
#else
printf("\tAtomic operations supported:\t\tNo\n");
#endif
#ifdef RTINST
printf("\tRuntime Instrumentation (slow code):\tYes\n");
#else