From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Jonathan Larmour <jifl@jifvik.org>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Lightweight C++ multithreaded exceptions
Date: Tue, 24 May 2005 09:01:00 -0000 [thread overview]
Message-ID: <1116873169.16697.17.camel@localhost.localdomain> (raw)
In-Reply-To: <42921638.1090405@jifvik.org>
> Your patches and instructions will certainly work in some situations. Some
> of it was using the code I included for our own C++ support anyway but did
> release :-), e.g. CYGPKG_LIBC_I18N_NEWLIB_CTYPE. But there are definitely
> a lot of gotchas once you introduce variation, including when you change
> 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.
--
Øyvind 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
next prev parent reply other threads:[~2005-05-23 18:32 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
2005-05-23 13:25 ` Øyvind Harboe
2005-05-24 8:48 ` Jonathan Larmour
2005-05-24 9:01 ` Øyvind Harboe [this message]
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=1116873169.16697.17.camel@localhost.localdomain \
--to=oyvind.harboe@zylin.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jifl@jifvik.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).