Brian Paul eaf9affa5e c11/threads: don't include assert.h if the assert macro is already defined ... In the gallium code, the assert() macro could come from either the system's assert.h file (via c11/threads.h) or from gallium's u_debug.h. It looks like all known assert.h files unconditionally #undef assert before defining their own version. So the assert you get depends on whether threads.h or u_debug.h was included last. In the gallium code we really want to use the assert() from u_debug.h (it behaves better on Windows). In gallium, c11/threads.h is only included after u_debug.h in the os_thread.h wrapper. So Adding an #ifndef assert test in the threads*.h files avoids using the system's assert(). Cc: "10.1" <mesa-stable@lists.freedesktop.org> Reviewed-by: José Fonseca <jfonseca@vmware.com>		2014-03-19 17:13:31 -06:00
..
threads.h	c11: Update docs/license.html and include verbatim copy of Boost license.	2014-01-23 12:55:55 +00:00
threads_posix.h	c11/threads: don't include assert.h if the assert macro is already defined	2014-03-19 17:13:31 -06:00
threads_win32.h	c11/threads: don't include assert.h if the assert macro is already defined	2014-03-19 17:13:31 -06:00