This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads
- From: "jason at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Apr 2005 18:28:32 -0000
- Subject: [Bug c++/13684] local static object variable constructed once but ctors and dtors called multiple times on same memory when called in multiple threads
- References: <20040114172507.13684.evijaykumar@yahoo.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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 -0000, "adah at netstd dot com" <gcc-bugzilla@gcc.gnu.org> wrote:
> I would like that
>
> * GCC provide extensions so that GCC users can use memory barriers and
> threading calls in a platform-independent way, and
I'd like that too.
> - Provide a command-line option (or pragma/attribute?) to disable/enable
> static initialization protection.
Already there: -fno-threadsafe-statics.
Jason
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13684