Home Original page

Why ld not read some non-virtual thunk in a import library or dll?

Brian Dessent brian@dessent.net
Tue Jul 8 06:31:00 GMT 2008 
Bo Yang wrote:

> And the only difference between two libxpcom_core.dll.a is that there
> is a @xx at the one which gcc 3.4.2 produce. I don't understand why

That @nn is the usual mangling for functions declared with the stdcall
calling convention.

> this "@xx" affect linkage. I hope my information make the problem

It affects linkage because the callsite expects the symbol to have the
correct mangling, but the compiler is emitting the symbol with the wrong
name.

> clearly. Help please, thanks!

This is PR27067 it would seem.  But that patch should be in 4.3, so I
don't know why it's failing here.  All I can suggest is using the MinGW
releases of gcc because they contain all the extra fixes that aren't in
the FSF tree yet.  In any case, not a binutils issue.

Brian
More information about the Binutils mailing list