versioning of _Unwind_*() symbols

[H. J. Lu]

On Tue, Apr 20, 2004 at 05:26:02PM -0700, Jim Wilson wrote:
> 
> What is wrong with putting the symbols back in libgcc_s.so?  If you link
> with libunwind before libgcc, programs will use the libunwind versions
> won't they?
> 

The old binaries don't know about libunwind.so. You can't load it
before libgcc_s.so transparently.

> Maybe the issue is that system libraries that were linked again libgcc
> will still use the libgcc version?  That gets us back to the issue I
> mentioned before, which is that this is really a system packaging issue,
> not a libgcc vesioning issue.  If a linux distro ships with libunwind as
> a standard package, then everything is OK.  If libunwind is an add on
> package, then we can't replace the versioned libgcc functions, we can
> only replace the internal unversioned functions.

It is more complicated than that. The end result is the new libgcc_s.so
is not 100% binary compatible with the old libgcc_s.so. There is no
easy way to fix it.


H.J.