This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: versioning of _Unwind_*() symbols


On Thu, Apr 22, 2004 at 04:34:25PM -0700, David Mosberger wrote:
> >>>>> On Thu, 22 Apr 2004 16:15:12 -0700, "H. J. Lu" <hjl@lucon.org> said:
> 
>   HJ> On Thu, Apr 22, 2004 at 03:12:32PM -0700, David Mosberger wrote:
>   >> >>>>> On Thu, 22 Apr 2004 15:02:15 -0700, "H. J. Lu" <hjl@lucon.org> said:
> 
>   HJ> BTW, since the ABI library is more than just unwind library. We
>   HJ> can't use David's unwind library as is.
> 
>   >> You can.  Just list -lunwind as a dependency as is done now with libgcc_s.
> 
>   HJ> I don't think it will work AS IS since linker may add libunwind.so to
>   HJ> DT_NEEDED if it is used. A new linker option may be needed to work
>   HJ> with it.
> 
> Ah, you're worried that linking against libcxa.so would cause a
> DT_NEEDED entry for libunwind.so in the _executable_?  I agree that's

It means you can't use a different ABI library which doesn't depend
on a separate unwind library.

> not ideal, but it's already happening with the Intel compiler, so in
> that sense it's nothing new.  If that could be avoided, I suppose it
> would be great.


H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]