From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26378 invoked by alias); 18 Apr 2005 18:28:37 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 26231 invoked by alias); 18 Apr 2005 18:28:32 -0000 Date: Mon, 18 Apr 2005 18:28:00 -0000 Message-ID: <20050418182832.26229.qmail@sourceware.org> From: "jason at redhat dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040114172507.13684.evijaykumar@yahoo.com> References: <20040114172507.13684.evijaykumar@yahoo.com> Reply-To: gcc-bugzilla@gcc.gnu.org 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 X-Bugzilla-Reason: CC X-SW-Source: 2005-04/txt/msg02456.txt.bz2 List-Id: ------- 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" 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