versioning of _Unwind_*() symbols

[H. J. Lu]

On Thu, Apr 22, 2004 at 02:39:37PM -0700, Mark Mitchell wrote:
> H. J. Lu wrote:
> 
> >>In any case, this issue is in the noise.  One key issue to solve is 
> >>getting libcxa.so out of libgcc, and putting just the ABI-required 
> >>symbols in that library.  Once that gets done, we can figure out what to 
> >>do next.   A second key issue is fixing the backwards compatibility 
> >>problem we already have due to the fact that the symbols in libgcc are 
> >>now versioned.  Let's work on those issues first.  Then, we can decide 
> >>whether or not to version the symbols in libcxa.
> >>   
> >>
> >
> >Those 2 issues are tied together. I think we may have to move to
> >libgcc_s.so.2. If we have more control over the ABI library, we may be
> >to able do something like:
> >
> >1. The ABI library provides separate entries for those backward
> >compatibility functions.
> >2. libgcc_s.so.1 defines those old backward compatibility functions
> >as wrappers of the real ones in the ABI library.
> > 
> >
> I'd rather see the ABI library contain just the functions the ABI 
> requires it to contain.  Put the backwards compatibility stuff in 
> libgcc.so.  I'm not sure about whether or not we need to bump the 
> version number on libgcc.so -- but I could believe that we have to do so.
> 

Are you suggesting to have 2 unwind libraries at run-time, one for
backwards compatibility in libgcc.so and the new one in the ABI
library?

BTW, since the ABI library is more than just unwind library. We
can't use David's unwind library as is. Also his unwind library
is a link-time replacement, not run-time replacement for existing
unwind library in icc.


H.J.