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: "paolo dot carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Jun 2009 11:07:14 -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 #10 from paolo dot carlini at oracle dot com 2009-06-07 11:07 -------
Benjamin, do you have a strong opinion about this issue? I don't, really, but
especially in the light of the C++0x drafts (thanks to Greg for pointing it
out), I would close for now the issue with a patch adding a configure time
option to not use the mutex, the current safe but slow behavior as default,
probably.
If I'm not mistaken, in either case the *.so would be binary compatible anyway.
In the future, we should probably move to the one global locale per thread, but
I don't think it's easily implementable without affecting the ABI...
--
paolo dot carlini at oracle dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paolo at gcc dot gnu dot
| |org, bkoz at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40088