public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "veloso at verylowsodium dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/40088] Creating a std::ostringstream object locks a global mutex
Date: Fri, 22 May 2009 21:03:00 -0000	[thread overview]
Message-ID: <20090522210306.30894.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40088-17695@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from veloso at verylowsodium dot com  2009-05-22 21:03 -------
(In reply to comment #4)
> 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)?

Pre C++0x, the standard says nothing about threads at all.

The C++0x draft has this to say:
Whether there is one global locale object for the entire program or one global
locale object per thread is implementation defined. Implementations are
encouraged but not required to provide one global locale object per thread. If
there is a single global locale object for the entire program, implementations
are not required to avoid data races on it


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40088


  parent reply	other threads:[~2009-05-22 21:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10  4:45 [Bug libstdc++/40088] New: " davewx7 at gmail dot com
2009-05-10  9:40 ` [Bug libstdc++/40088] " paolo dot carlini at oracle dot com
2009-05-10 10:14 ` paolo dot carlini at oracle dot com
2009-05-10 10:42 ` paolo dot carlini at oracle dot com
2009-05-10 11:53 ` rguenth at gcc dot gnu dot org
2009-05-10 12:12 ` rguenth at gcc dot gnu dot org
2009-05-10 12:14 ` rguenth at gcc dot gnu dot org
2009-05-10 12:21 ` rguenth at gcc dot gnu dot org
2009-05-10 12:34 ` paolo dot carlini at oracle dot com
2009-05-22 21:03 ` veloso at verylowsodium dot com [this message]
2009-06-07 11:07 ` paolo dot carlini at oracle dot com
2009-12-17 11:12 ` paolo dot carlini at oracle dot com
2009-12-18  9:41 ` paolo at gcc dot gnu dot org
2009-12-18  9:51 ` paolo dot carlini at oracle dot com
2009-12-18  9:58 ` paolo dot carlini at oracle dot com
2009-12-22 10:09 ` paolo dot carlini at oracle dot com
     [not found] <bug-40088-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 10:02 ` jackie.rosen at hushmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090522210306.30894.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).