From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28369 invoked by alias); 23 May 2005 10:19:09 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 28252 invoked by uid 22791); 23 May 2005 10:19:03 -0000 Received: from asav1.lyse.net (HELO asav1.lyse.net) (213.167.96.68) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 23 May 2005 10:19:03 +0000 Received: from asav1.lyse.net (asav1.lyse.net [127.0.0.1]) by localhost.lyse.net (Postfix) with ESMTP id 53D87902A7; Mon, 23 May 2005 12:14:33 +0200 (CEST) Received: from mail1.lyse.net (unknown [192.168.42.2])by asav1.lyse.net (Postfix) with ESMTPid 3DF8A90263; Mon, 23 May 2005 12:14:33 +0200 (CEST) Received: from [84.234.138.230] (helo=[192.168.0.193])by mail1.lyse.net with smtp (Exim 4.34)id 1DaA0O-0001qX-M1; Mon, 23 May 2005 12:17:52 +0200 From: =?ISO-8859-1?Q?=D8yvind?= Harboe To: Jerome Souquieres Cc: ecos-discuss@sources.redhat.com In-Reply-To: <4291A7C3.5000801@kis.fr> References: <1116664216.28556.45.camel@localhost.localdomain> <4291A7C3.5000801@kis.fr> Content-Type: text/plain; charset=ISO-8859-1 Date: Mon, 23 May 2005 13:25:00 -0000 Message-Id: <1116843565.19282.8.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-imss-version: 2.025 X-imss-result: Passed X-imss-scores: Clean:57.84895 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:2 C:1 M:1 S:1 R:1 (0.1500 0.1500) Subject: Re: [ECOS] Lightweight C++ multithreaded exceptions X-SW-Source: 2005-05/txt/msg00299.txt.bz2 On Mon, 2005-05-23 at 11:52 +0200, Jerome Souquieres wrote: >=20 > That's interesting. However, from what I understand, this approach=20 > only solves the multithreaded exceptions problem. This does nothing to > ensure that the standard C++ library (including STL) is thead safe. Am > I right ? I know there are some atomicity issues, but is that already handled in a CPU architecture specific but os-independent fashion by default in libstdc++? Does anyone know of a definitive list of issues w.r.t. libstdc++ & multithreading? I guess the fact that eCosCentric is destined to contribute their libstdc++ support saps my initiative for contributing patches in this area. Even more so, because I have a solution for my needs. --=20 =D8yvind Harboe http://www.zylin.com -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss