On Jan 4, 2015, at 9:00 AM, Bernd Edlinger <bernd.edlin...@hotmail.de> wrote: > It is due to a race condition in tsan itself, it cannot decide which access > was the > previous one and which was the second one, but our tsan tests are not meant as > a functional test of the tsan runtime library, they are only meant to test > the GCC > instrumentation.
Well, at least one test case that _is_ a functional test of the tsan runtime library isn’t a bad idea.