------- Additional Comments From adah at netstd dot com 2005-02-03 03:30 ------- I am not David but let me try to name some possible objections.
* The current code is unsafe on some architectures (DLCP is unsafe) * For cross-compiler code, users SHOULD have already locked a mutex before entering the function that might have race conditions: so there will be unnecessary overhead * If users do not use a mutex, if might well be the case that the specific function will be called by only one thread; or that the function has been called at least once in the initialization (one thread only) code; and the "fix" creates unnecessary overhead again Granted, there is no standard C++ API for threading. But when users write a multi-threaded program, they have already begun to use non-standard threading APIs. They might well use the APIs to protect what this fix tries to do. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13684
