From: Skluzacek, Christian (C.Skluzacek++at++fokkerspace.nl)
Date: 08/16/2001 04:30:28
AFAIK it is alright to mix c libraries from different compilers(does anyone
else know differently?). As you said, the initialization of c++ as well as
other things are handled differently between compilers so the name mangling
inconvenience is also actually a benefit by preventing you from mixing
things that shouldn't be mixed. But I think we're getting off topic here....
Chris
> ----------
> From: Brian Corrie[SMTP:brian.corrie++at++newmic.com]
> Sent: Wednesday, 15 August, 2001 18:30
> To: Skluzacek, Christian; info-performer++at++sgi.com; Surakle++at++gmx.de
> Subject: RE: Loader II
>
>
> Hello pfAll,
>
> I think that the gcc compilers used the SGI backends to generate code, and
> therefore calling code between MIPS CC and gcc compilers should work. I
> think I have done this in the past with C code with no problems (in fact,
> I
> think it was calling a gcc compiled C library from a CC compiled C++
> application), but I am less sure about C++ to C++. Since CC -> gcc works
> it
> may be a name mangling issue so if you can get g++ to match CC's name
> mangling it may work. Since it is seg faulting and not dying because of
> undefined symbols, it may not be a name mangling problem but instead be a
> problem with the different way the two compilers do the initialization of
> static instances of classes etc. The initialization phase of C++ code is
> much more complex than C and there is a possibility that two compilers do
> incompatible things.
>
> Just my thoughts on the matter, take em or leave em 8-)
>
> Cheers,
>
> Brian
>
This archive was generated by hypermail 2b29 : Thu Aug 16 2001 - 04:31:51 PDT