libgcc problems

Andrey Slepuhin pooh@msu.net
Mon Jan 19 15:31:00 GMT 1998


On 19-Jan-98 David Edelsohn wrote:
>>>>>> Andrey Slepuhin writes:
> 
> Andrey> I'm also worried about duplicated __tiPc symbol. What does it mean?
> Andrey> should I prevent exporting it in collect2?
> 
>       I have no ideas about the origin or purpose of this symbol.

I guess that this is typeinfo function for char*, i.e I should
disable exporting all typeinfo functions in collect2. But what other
automatically generated symbols I should disable for export?
I'm slightly confused with this situation because there are
two possible solutions:
1) To disable export of automatically generated symbols or to make
   non-global. This solution leads to some duplicated code, but
   avoids overhead with global calls.
2) To export automatically generated symbols and to resolve
   conflicts using -frepo option, which currently resolves
   only template conflicts.

Any opinion?

Andrey.




More information about the Gcc mailing list