[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13684 Jackie Rosen jackie.rosen at hushmail dot com changed: What|Removed |Added CC|

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- Additional Comments From adah at netstd dot com 2005-04-18 09:06 --- Function calls, memory barriers, (and lock operations?) are all overheads. I would like that * GCC provide extensions so that GCC users can use memory barriers and threading calls in a platform-independent way,

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- Additional Comments From jason at redhat dot com 2005-04-18 18:28 --- Subject: Re: local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads On 18 Apr 2005 09:07:00 -, adah at netstd dot com [EMAIL

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- Additional Comments From jason at redhat dot com 2005-04-14 07:38 --- Subject: Re: local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads DCL with explicit memory barriers is safe. That's what I'm

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- Additional Comments From dhruvbird at yahoo dot com 2005-04-13 16:56 --- (In reply to comment #19) I want to emphasize here again one principle of C and C++: Trust the programmers, and allow them to do low-level tunings for performance. Or what is the purpose of C++ (when

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- 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

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- 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

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- 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

[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads

--- Additional Comments From adah at netstd dot com 2005-02-03 03:42 --- I want to emphasize here again one principle of C and C++: Trust the programmers, and allow them to do low-level tunings for performance. Or what is the purpose of C++ (when compared with high-level languages