Mangling bug in Forte 6.1 Update 1 ?

Question

Hi,
I built the following code
Foo.h >>>>>>>>>>>>>>>>>>>>
class Foo
public:
typedef Foo Bar;
void mangle( const Foo&, const Bar& );
<<<<<<<<<<<<<<<<<<<<<<<
Foo.c >>>>>>>>>>>>>>>>>>
#include "Foo.h"
// Version 1
void Foo::mangle( const Foo&, const Foo::Bar& ) { }
// Version 2
// void Foo::mangle( const Foo&, const Foo& ) { }
<<<<<<<<<<<<<<<<<<<<<<<<
The strange thing is the both version 1 and 2 of the implementation of the
method compile with "CC -C Foo.c", as I think is correct.
However they mangle to different symbols in the resulting .o file
Version 1 : __1cDFooGmangle6Mrk0r1_v_
Version 2 : __1cDFooGmangle6Mrk02_v_
Both these symbols demangle to : "void Foo::mangle(const Foo&,const Foo&)"
I a real world example this caused us some stange link time failures.
Am I right in thinking the both implementations are allowed and that
this a compiler bug?
David Hunter
Lehman Brothers

Answer 1

Hi,
I am not C++ guru, So I don't whether this is a bug or not.
But, in past somebody had given following workarounds
to me:
1. Use typedefs everywhere or nowhere.
2. Use Pragma weak, specifying the mangled names as quoted strings.
3. Use "-Qoption ccfe -abiopt=mangle6" . Note, however, that this option may prevent linking with some libraries.
Hope this helps.
Thanks
Kalpesh