This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/55561] TSAN: provide a TSAN instrumented libgomp
- From: "roland at rschulz dot eu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 08 May 2014 19:49:11 +0000
- Subject: [Bug sanitizer/55561] TSAN: provide a TSAN instrumented libgomp
- Auto-submitted: auto-generated
- References: <bug-55561-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561
Roland Schulz <roland at rschulz dot eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |roland at rschulz dot eu
--- Comment #44 from Roland Schulz <roland at rschulz dot eu> ---
If I run tsan on our code with libgomp compiled with --disable-linux-futex, I
only see false positives for omp-atomic constructs. Everything else seems fine.
If I compile libgomp with tsan and without --disable-linux-futex I get a lot of
false positives. And if I compile libgomp with both tsan and
--disable-linux-futex, I get also the false positives for omp-atomic. I used
gcc 4.8.2.
For those who reported success with compiling libgomp with tsan:
- Do you also use --disable-linux-futex or did you only use -fsanitize=thread?
- Did you test with code using "#pragma omp atomic update"?
Is there a way to compile libgomp to not get false positives for omp-atomic?