Aehm, sorry, that's the sporadic failure, I mentioned:
https://gcc.gnu.org/ml/gcc-regression/2015-01/msg00041.html New failures: FAIL: g++.dg/tsan/aligned_vs_unaligned_race.C -O2 execution test New passes: https://gcc.gnu.org/ml/gcc-regression/2015-01/msg00044.html New failures: New passes: FAIL: g++.dg/tsan/aligned_vs_unaligned_race.C -O2 execution test Really I did run this test often, before I checked it in, but... 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. For the purpose of finding race conditions in an application a detection likelihood of 98% is absolutely perfect, just for our test suite that causes unnecessary failures. So, I still think I should fix that test case, maybe with a comment, why I have to sleep(1), what do you think? Bernd.
patch-tsan-race.diff
Description: Binary data
