------- Additional Comments From gianni at mariani dot ws 2005-02-03 01:56 ------- > 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.
This approach makes it very difficult to use library code that would otherwise be thread safe. Since there is no standard C++ API for threading, resolving this issue would otherwise cause a significant dependantcy on external libraries, not to mention the potential bugs that arise from ad-hoc fixes. (like deadlocks). The only way to truly resolve this is to ensure proper functioning code is to have the compiler generate code that adheres to the letter of the C++ standard, even in a multi-threaded environment. Why do you object to havingthe compiler generate MT safe code ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13684
