Re: libsupc++, _cxa references, and Dinkum libcpp

[Joe Buck <jbuck@synopsys.com>]

On Fri, May 16, 2003 at 09:07:31PM -0000, gp@qnx.com wrote:
> I'm working on porting gcc-3.2.3 to the various QNX platforms.  We use both
> libstdc++ and Dinkumware libcpp for C++.  The difficulty here is that gcc
> (actually cc1plus I think) is emitting __cxa* symbols, like the call:
> 
>   push_throw_library_fn (get_identifier ("__cxa_call_unexpected"), tmp);
> 
> in gcc/cp/except.c:init_exception_processing().  So when I build the
> Dinkumware with gcc-3.2.3, the libcpp ends up with these undefined references
> to various __cxa symbols.  These symbols are in libsupc++, but so are a number
> of other symbols that conflict with the Dinkumware.

Which symbols conflict?  Is Dinkumware attempting to provide fundamental
C++ support routines such as the default operator new?  If so, then
there's likely to be more work to do than just separating symbols, since
you'll need to have support library functions that correctly interact with
whatever Dinkumware provides.