From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28117 invoked by alias); 20 May 2005 10:01:22 -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 27918 invoked from network); 20 May 2005 10:01:05 -0000 Received: from unknown (HELO asav1.lyse.net) (213.167.96.68) by sourceware.org with SMTP; 20 May 2005 10:01:05 -0000 Received: from asav1.lyse.net (asav1.lyse.net [127.0.0.1]) by localhost.lyse.net (Postfix) with ESMTP id 2AFF290294; Fri, 20 May 2005 11:56:40 +0200 (CEST) Received: from mail1.lyse.net (unknown [192.168.42.2])by asav1.lyse.net (Postfix) with ESMTPid 147FD901D1; Fri, 20 May 2005 11:56:40 +0200 (CEST) Received: from [84.234.138.230] (helo=[192.168.0.193])by mail1.lyse.net with smtp (Exim 4.34)id 1DZ4IO-0001nl-5H; Fri, 20 May 2005 11:59:56 +0200 From: =?ISO-8859-1?Q?=D8yvind?= Harboe To: "Neundorf, Alexander" Cc: ecos-discuss@sources.redhat.com In-Reply-To: <5A8A17126B73AC4C83968F6C4505E3C5021A7D1D@JO-EX01.JENOPTIK.NET> References: <5A8A17126B73AC4C83968F6C4505E3C5021A7D1D@JO-EX01.JENOPTIK.NET> Content-Type: text/plain; charset=ISO-8859-1 Date: Fri, 20 May 2005 15:04:00 -0000 Message-Id: <1116583290.10422.45.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:99.90000 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: AW: [ECOS] Re: C++ Support X-SW-Source: 2005-05/txt/msg00280.txt.bz2 On Fri, 2005-05-20 at 11:11 +0200, Neundorf, Alexander wrote: > Hi, >=20 > > Von: ecos-discuss-owner@ecos.sourceware.org > ... > > I'm using both STLport and libstdc++ w/eCos. > >=20 > > It isn't supported out of the box, but it isn't too hard to get it > > working and I haven't seen any problems once up and running.=20 > >=20 > > The instructions are a bit crude and there are some somewhat > > questionable steps due to newlib/eCos issues, but you can=20 > > always buy the > > eCosPro kit if you want something that is fully tested and=20 > > works out of > > the box :-) > >=20 > > http://www.zylin.com/libstdc++.html > > http://www.zylin.com/stlport.html >=20 > Can you compare both ? Code size, execution speed, memory consumption, ge= neral impression, problems, etc. ? No appreciable difference in code size and I haven't tested performance. The main reason I wanted to get libstdc++ working was that at some point I want to switch to GCC 3.4.2 for new projects and the STLport guys haven't taken an interest in eCos support AFAICT. Presumably libstdc++ support would work for future GCC versions without much effort as compared to STLport. My impression is that libstc++ is more heavily tested(ref. libstdc++ GCC testsuite on a raft of platforms) and there is a consensus(pthreads) on how to support multithreaded exceptions. > > For the libstdc++ stuff I submitted a patch to eCos w.r.t. some issues > > with using C++ early in eCos startup, but it didn't receive=20 > > any comments > > so far: > >=20 > > http://ecos.sourceware.org/ml/ecos-patches/2005-04/msg00007.html >=20 > I guess you should post again :-) Well.... I wonder. eCosPro contains libstdc++ support. So... ? --=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