http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561
--- Comment #22 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2012-12-30 09:03:15 UTC --- (In reply to comment #18) > > The obvious solution to this seems to be that also the OMP runtime (libgomp) > > must be compiled with '-fsanitize=thread. If I do that, it appears to work. > > That's cool, I will try to do some more testing. > > Good idea! > 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.
