This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/31117] c++locale.o thread-unsafe in libstdc++
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Mar 2007 20:46:47 -0000
- Subject: [Bug libstdc++/31117] c++locale.o thread-unsafe in libstdc++
- References: <bug-31117-9156@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from pcarlini at suse dot de 2007-03-10 20:46 -------
Humm, I'm afraid this is basically a WONTFIX or at least WONTFIX-ANY-TIME-SOON,
because we talking about targets using the GENERIC locale model, where, at
variance with the GNU locale model, on which we are focused of course, no
guarantees are provided about locales vs thread-safety: if you look at those
template functions, before the "detail" of errno you will notice that the
setlocale function is called everywhere and that is definitely not thread-safe,
accessing a global locale setting...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31117