versioning of _Unwind_*() symbols

[Mark Mitchell]

H. J. Lu wrote:

>Your example shows how versioning will help here. If the existing
>programs can't pass the security audit without recompiling after
>fixing the ABI implemenation, we can change the version without
>providing the old version for backward compatibilty, those programs
>won't post a security risk since they can't run. Or we can put
>a warning message in the old version if the risk is relatively low.
>
>Without versioning, it won't be easy to fix the security bug in the
>implemenation.
>  
>
I understand your argument, but I don't find it compelling.  Doing what 
you suggest would cause a lot of programs that work just fine -- with or 
without the change -- to stop working.

I think it's time for us to agree to disagree.

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.

-- 
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com