On Aug 27, 2009, at 9:33 AM, Julian Seward wrote: > >> I'm using helgrind from 3.5.0 on OPENMP code. >> >> I have a lazily malloc'd pthread mutex in a static global >> variable that helgrind detects. >> >> I'd like to disable the warning somehow in code, not >> with a suppression, so that I can look at more interesting >> errors. > > You can't use Helgrind properly on gcc/g++ compiled OpenMP code as-is, > because it doesn't understand the custom synchronisation primitives > used by libgomp.so, the support library. >
Ah yes. I read that warning but did not (and do not) have sufficient experience with the OpenMP #pragma voo-doo to understand the failure symptoms. ATM I have exactly 4 #pragma statements, and I've been assuming that since helgrind so no issues with one #pragma that Fedora had compiled libgomp to use -lpthread. But the spurious false positives from helgrind are exactly in the places where I would expect complaints if futexes instead of mutexes were in use. Time to do my homework ... Helgrind looks like a very promising tool for figuring OpenMP. The #pragma instrumentation is the tip of a rather large parallelizing iceberg, and the the data scoping and scheduling primitives available in OpenMP are rather obscure and arcane even if complete. Without a tool like Helgrind, one is forced to have a very deep understanding of the inner secrets of OpenMP implementations. Thanks for the hint. 73 de Jeff ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
