This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Will glibc support optional STT_COMMON lookup?
- From: Jakub Jelinek <jakub at redhat dot com>
- To: "H.J. Lu" <hjl at lucon dot org>
- Cc: Carmelo Amoroso <carmelo73 at gmail dot com>, Nick Clifton <nickc at redhat dot com>, binutils at sourceware dot org, GNU C Library <libc-alpha at sources dot redhat dot com>
- Date: Wed, 10 Oct 2007 15:09:09 +0200
- Subject: Re: Will glibc support optional STT_COMMON lookup?
- References: <20071003140350.GA19346@lucon.org> <470B930C.4030201@redhat.com> <20071009144909.GA30447@caradoc.them.org> <470B9949.4070406@redhat.com> <20071009155954.GB30781@lucon.org> <470BA6D7.4080808@redhat.com> <20071009161334.GA30871@lucon.org> <20071009163720.GA31164@lucon.org> <2ccd6e3c0710092329p33b42a50t75a3732914484483@mail.gmail.com> <20071010125352.GA9402@lucon.org>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Wed, Oct 10, 2007 at 05:53:52AM -0700, H.J. Lu wrote:
> If I am not mistaken, glibc treates STT_COMMON the same as STT_OBJECT.
Right.
> That means the optional STT_COMMON lookup isn't supported. There
> is no point to generate STT_COMMON in executable and shared library.
Yep. I don't think it would be a good idea to slow down the dynamic
lookup for this, especially if STT_COMMON would be generated for all
common vars rather than only when asked for it by some new attribute.
That would throw us back to the LD_DYNAMIC_WEAK=1 times.
Jakub