On Sun, Jan 04, 2015 at 11:07:31AM -0800, Mike Stump wrote:
> On Jan 4, 2015, at 9:00 AM, Bernd Edlinger <[email protected]> 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.
The GCC instrumentation can be tested just by scanning the *.optimized dumps
or assembly. And perhaps the runtime test just be hidden by some special
environment variable that the user acks he doesn't main spurious FAILs.
Jakub
