------- Additional Comments From davids at webmaster dot com 2005-02-02 23:22 ------- This is not a GCC bug and should not be fixed in GCC. The bug is in the test code which accesses an object that is shared by multiple threads without proper mutexes. Period. End of story.
The correct fix is to acquire a mutex before calling a function that might accessed shared data (and constructing a static object counts). This should be common sense, and it's surprising to me that it is not. Anyone can create code that fails if you call functions that manipulate shared data without holding any mutexes. DS -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13684
