public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: Colin.Spier@pipinghotnetworks.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] C++ standard libraries
Date: Wed, 13 Sep 2000 07:44:00 -0000	[thread overview]
Message-ID: <200009131444.PAA01699@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <39BF8BE9.B6793F2C@redhat.com>

>>>>> "Jifl" == Jonathan Larmour <jlarmour@redhat.com> writes:

    Jifl> Colin Spier wrote:
    >> 
    >> Do you think that there is a significant amount of work involved?
    >> 
    >> Where might one start?

    Jifl> I think it's several weeks worth of work.

    <snip lots of good information>

For more details on libstdc++ development and mailing lists you may
want to look at http://sources.redhat.com/libstdc++/ , although the
code has now been incorporated into the mainline gcc sources.

Another possible concern is that eCos itself is currently compiled
with -fno-rtti -fno-exceptions. This could give problems if you start
mixing eCos and libstdc++ header files, since the latter will
definitely require exceptions and probably rtti as well. It is
possible that eCos will just work if you build it with rtti and
exceptions, but that is untested and obviously there would be some
code size penalties.

Bart Veer // eCos net maintainer

  reply	other threads:[~2000-09-13  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-08  7:16 Colin Spier
2000-09-10 20:35 ` Jonathan Larmour
2000-09-13  2:26   ` Colin Spier
2000-09-13  7:15     ` Jonathan Larmour
2000-09-13  7:44       ` Bart Veer [this message]
2000-09-13 14:15         ` Dave Vogel

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=200009131444.PAA01699@sheesh.cygnus.co.uk \
    --to=bartv@redhat.com \
    --cc=Colin.Spier@pipinghotnetworks.com \
    --cc=ecos-discuss@sourceware.cygnus.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).