From: Jerome Souquieres <jerome.souquieres@kis.fr>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Lightweight C++ multithreaded exceptions
Date: Mon, 23 May 2005 12:52:00 -0000 [thread overview]
Message-ID: <4291A7C3.5000801@kis.fr> (raw)
In-Reply-To: <1116664216.28556.45.camel@localhost.localdomain>
Øyvind Harboe wrote:
>One approach to supporting multithreaded exceptions that seem to work
>quite well in my experience is to use the single threaded GCC toolchain,
>but to make the the global variable in C++ exceptions, fc_static, per
>thread.
>
That's interesting. However, from what I understand, this approach
only solves the multithreaded exceptions problem. This does nothing to
ensure that the standard C++ library (including STL) is thead safe. Am I
right ?
--
Jerome Souquieres
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-05-23 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 9:13 Øyvind Harboe
2005-05-23 12:52 ` Jerome Souquieres [this message]
2005-05-23 13:25 ` Øyvind Harboe
2005-05-24 8:48 ` Jonathan Larmour
2005-05-24 9:01 ` Øyvind Harboe
2005-05-24 9:13 ` Paul D. DeRocco
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=4291A7C3.5000801@kis.fr \
--to=jerome.souquieres@kis.fr \
--cc=ecos-discuss@sources.redhat.com \
--cc=oyvind.harboe@zylin.com \
/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).