From: Daniel Kegel <dank@kegel.com>
To: Ciorecan.Marius@ssi-schaefer.ro
Cc: gcc@gcc.gnu.org
Subject: RE: Multithreading problems
Date: Tue, 07 Dec 2004 01:24:00 -0000 [thread overview]
Message-ID: <41B5064C.4030503@kegel.com> (raw)
Ciorecan.Marius@ssi-schaefer.ro wrote:
> is libstdc++ not thread safe?
The current versions of gcc come with versions of
libstdc++ that provide 'thread safety' as defined
in http://www.sgi.com/tech/stl/thread_safety.html, I think.
Note that this is not as 'thread safe' as Java's containers are.
It also doesn't mean you can't shoot yourself in
the foot with threads.
- Dan
next reply other threads:[~2004-12-07 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 1:24 Daniel Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-06 17:30 Ciorecan Marius
2004-12-06 15:37 Ciorecan Marius
2004-12-06 17:26 ` David Edelsohn
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=41B5064C.4030503@kegel.com \
--to=dank@kegel.com \
--cc=Ciorecan.Marius@ssi-schaefer.ro \
--cc=gcc@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).