From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12125 invoked by alias); 23 May 2005 18:32:34 -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 12094 invoked by uid 22791); 23 May 2005 18:32:26 -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 18:32:26 +0000 Received: from asav1.lyse.net (asav1.lyse.net [127.0.0.1]) by localhost.lyse.net (Postfix) with ESMTP id 5AB5E903F5; Mon, 23 May 2005 20:27:56 +0200 (CEST) Received: from mail1.lyse.net (unknown [192.168.42.2])by asav1.lyse.net (Postfix) with ESMTPid 480CE903E9; Mon, 23 May 2005 20:27:56 +0200 (CEST) Received: from [84.234.138.230] (helo=[192.168.0.193])by mail1.lyse.net with smtp (Exim 4.34)id 1DaHhr-0004qT-R8; Mon, 23 May 2005 20:31:16 +0200 From: =?ISO-8859-1?Q?=D8yvind?= Harboe To: Jonathan Larmour Cc: ecos-discuss@sources.redhat.com In-Reply-To: <42921638.1090405@jifvik.org> References: <1116664216.28556.45.camel@localhost.localdomain> <4291A7C3.5000801@kis.fr> <1116843565.19282.8.camel@localhost.localdomain> <42921638.1090405@jifvik.org> Content-Type: text/plain; charset=ISO-8859-1 Date: Tue, 24 May 2005 09:01:00 -0000 Message-Id: <1116873169.16697.17.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:49.25300 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/msg00307.txt.bz2 > Your patches and instructions will certainly work in some situations. Som= e=20 > of it was using the code I included for our own C++ support anyway but di= d=20 > release :-), e.g. CYGPKG_LIBC_I18N_NEWLIB_CTYPE. But there are definitely= =20 > a lot of gotchas once you introduce variation, including when you change= =20 > to different architectures or try to use the libstdc++ library itself. I haven't taken my stuff through the libstdc++ testsuite. Mainly because there is very little point. It does what I need and eCosCentric is destined to release libstdc++ before these issues affect me. Or possibly things will linger long enough that I make one more pass over the libstdc++ stuff. No point in spending time until I know whether it is necessary :-) I've counted at least three projects that went from eCos to MMU-less Linux variants when they tried to get STL to work(all had oodles of RAM, which gives eCos less of an edge anyway) and I know there are at least a handful of people using my hacked up stopgap solution.=20 --=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