libgcc problems with shared libraries
David Edelsohn
dje@watson.ibm.com
Thu Jan 15 16:06:00 GMT 1998
>>>>> Andrey Slepuhin writes:
Andrey> Moreover, it seems to me that some symbols in libgcc, if linked
Andrey> into a shared library, cannot be exported, at least this permanently
Andrey> cause AIX linker to generate invalid executables with the diagnostic
Andrey> like the following:
Andrey> ld: 0711-768 WARNING: Object /tmp/ccQj2qqa1.o, section 1, function ._savef14:
Andrey> The branch at address 0x8 is not followed by a recognized no-op
Andrey> or TOC-reload instruction. The unrecognized instruction is 0x91A1FF24.
Andrey> adding -fPIC option during libgcc build doesn't have any effect (and as I
Andrey> understand, it is not needed on powerpc systems).
None of these problems you are reporting are GCC code generation
bugs, they are collect2 exporting bugs. AIX has an export list for a
reason and GCC collect2 is subverting that policy. Some symbols are
special and collect2 is blindly re-exporting them.
[I cannot send email directly to Andrey from this address for some
reason and none of my replies to egcs have appeared back on the list
although I am receiving other egcs mailings.]
David
More information about the Gcc
mailing list