From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32479 invoked by alias); 5 Sep 2004 03:19:32 -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 32462 invoked by uid 48); 5 Sep 2004 03:19:31 -0000 Date: Sun, 05 Sep 2004 03:19:00 -0000 Message-ID: <20040905031931.32461.qmail@sourceware.org> From: "adah at netstd 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: 2004-09/txt/msg00405.txt.bz2 List-Id: ------- Additional Comments From adah at netstd dot com 2004-09-05 03:19 ------- I myself have had headaches about this problem (unsafe DLCP) too. Indeed, I do not have problems with DLCP, since I have access only to IA-32 platforms, but I really like to make my code more portable. Currently there is no known way to make memory barriers portable. So I guess it might be a good idea that GCC provide built-in functions to do the job. On IA-32 platforms it is a just a null operation, but on other systems it might really do significant stuff. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |adah at netstd dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13684