http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561
--- Comment #23 from Dmitry Vyukov <dvyukov at google dot com> 2012-12-30 09:57:44 UTC --- (In reply to comment #22) > I did do some more testing, and the combination '-fsanitize=thread -fopenmp' > was really very useful. Apart from the libgomp-related warning discussed here > and PR40362, everything worked well, and I was able to find a couple of > correctly identified OMP bugs in our code that would have been (in part) very > difficult to find without the tool. I'll also allow us to start an automatic > regression tester for our OMP code, which is something we didn't manage so > far. > > I would be great to get this combination to work out-of-the-box. Wow! Great news! I am not really a gcc hacker. Perhaps Jakub or Dodji can help. It would be interesting to run some OpenMP test suite with tsan to test libgomp better (various schedules and clause types -- section, task, single, etc). Later we may want to instrument libgomp in one way or another to provide better detection and reporting.
