From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26513 invoked by alias); 10 May 2009 11:53:07 -0000 Received: (qmail 26490 invoked by uid 48); 10 May 2009 11:52:54 -0000 Date: Sun, 10 May 2009 11:53:00 -0000 Message-ID: <20090510115254.26489.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/40088] Creating a std::ostringstream object locks a global mutex In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rguenth at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-05/txt/msg00821.txt.bz2 ------- Comment #4 from rguenth at gcc dot gnu dot org 2009-05-10 11:52 ------- Hm. I wonder how the "global" locale is supposed to interact with multiple threads anyway (in the face of C++ not knowing about threads). Would it be a conforming implementation to put the global locale into thread-local storage (thus, having a "global" locale for each thread)? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40088