public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5467: STL problem using multithreading
Date: Wed, 23 Jan 2002 08:46:00 -0000 [thread overview]
Message-ID: <20020123164603.9123.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5467; it has been noted by GNATS.
From: Carlo Wood <carlo@alinoe.com>
To: jjessel@amadeus.net
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/5467: STL problem using multithreading
Date: Wed, 23 Jan 2002 17:38:43 +0100
On Wed, Jan 23, 2002 at 04:17:47PM -0000, jjessel@amadeus.net wrote:
> >Number: 5467
You posted four Problem reports - duplicates as far as I can see.
> I have isolated the following code (that I suppose to be thread safe) in order to reproduce a problem I have in a bigger program.
> I try to execute it in several threads.
Please provide a working example, that is: a program with main()
that compiles out of the box and shows the problem.
> Here is my compilation line:
> g++ -g -fexceptions simple.cpp -o simple -lpthread
You should use:
g++ -pthread -g -fexceptions simple.cpp -o simple
The option -pthread will cause the library to be
thread-safe.
Also, std::cout is not thread-safe (and not intended to), you need
to provide a user-level lock for it.
--
Carlo Wood <carlo@alinoe.com>
next reply other threads:[~2002-01-23 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 8:46 Carlo Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 8:57 ljrittle
2002-01-23 8:26 jjessel
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=20020123164603.9123.qmail@sources.redhat.com \
--to=carlo@alinoe.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).