https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561
--- Comment #49 from Dmitry Vyukov <dvyukov at google dot com> --- > However, my first idea would be that, since libgomp is not sanitized, not all > races in 'user land' would be detected. I'm just guessing ... If libgomp does not access user data (which I suspect it does not generally do), then un-instrumented libgomp can only lead to false positives due to missed synchronization in libgomp. The missed synchronization can come mostly from atomic operations, because tsan intercepts pthread_mutex and other library functions.
