This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/40088] Creating a std::ostringstream object locks a global mutex
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 May 2009 11:52:54 -0000
- Subject: [Bug libstdc++/40088] Creating a std::ostringstream object locks a global mutex
- References: <bug-40088-17695@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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