[ECOS] C++ standard libraries

Jonathan Larmour jlarmour@redhat.com
Wed Sep 13 07:15:00 GMT 2000


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

I think it's several weeks worth of work.

The first problem is that libstdc++ is integrated with the compiler - and
eCos is not around at compiler build time. Therefore the first step is to
ensure that what gcc builds at compiler build time will work with eCos, no
matter what the configuration (more or less).

libstdc++ relies heavily on exceptions. But exceptions are not thread-safe
by default - gcc would have to have work done on it to make it thread-safe
in eCos. The real challenge here is that since eCos is configurable, it
needs to do the right thing when the eCos kernel is not present either!

The other area to pay attention to is libio - libstdc++ requires libio. The
difficulty is that to make libstdc++ standards-compliant, I/O from
libstdc++ and I/O from normal libc stdio functions must be interleaved.
This means that they must use the same implementation. libstdc++ can only
work with libio, so the issue becomes one of integrating libio and eCos.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault


More information about the Ecos-discuss mailing list