From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21867 invoked by alias); 14 May 2014 19:25:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 21798 invoked by uid 48); 14 May 2014 19:25:19 -0000 From: "dvyukov at google dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/55561] TSAN: provide a TSAN instrumented libgomp Date: Wed, 14 May 2014 19:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dvyukov at google dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-05/txt/msg01332.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561 --- Comment #49 from Dmitry Vyukov --- > 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.