public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davewx7 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/40088]  New: Creating a std::ostringstream object locks a global mutex
Date: Sun, 10 May 2009 04:45:00 -0000	[thread overview]
Message-ID: <bug-40088-17695@http.gcc.gnu.org/bugzilla/> (raw)

When a std::ostringstream object is created, it references a locale object
which is synchronized by a global mutex.

This causes a significant performance problem for multi-threaded applications
running on systems with many CPU's if they use string streams frequently.


-- 
           Summary: Creating a std::ostringstream object locks a global
                    mutex
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: davewx7 at gmail dot com


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


             reply	other threads:[~2009-05-10  4:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10  4:45 davewx7 at gmail dot com [this message]
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
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

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=bug-40088-17695@http.gcc.gnu.org/bugzilla/ \
    --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).