libgcc problems

[Andrey Slepuhin]

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

It seems that at least there are some exceptions to this rule (as with
__terminate_func, which should be available anywhere to be accessed
from inline set_terminate()).

Andrey.