Re: [PATCH v2 3/4] configure: Disable lazy binding by default

["Andreas K. Huettel" <dilfridge@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]

Am Montag, 17. Juli 2023, 17:55:35 CEST schrieb Siddhesh Poyarekar via Libc-alpha:
> On 2023-07-17 11:30, Florian Weimer via Libc-alpha wrote:
> > * Siddhesh Poyarekar:
> > 
> >> On 2023-07-13 05:38, Florian Weimer via Libc-alpha wrote:
> >>> * Siddhesh Poyarekar via Libc-alpha:
> >>>
> >>>> +‘--disable-bind-now’
> >>>> +     Enable lazy binding for installed shared objects and programs.
> >>>> +     Lazy binding may improve program load times but it will disable
> >>>> +     security hardening that enables full RELRO and a read-only global
> >>>> +     offset table (GOT).
> >>> This description is not correct because as far as I can see,
> >>> --disable-bind-now does not enable lazy binding if the toolchain or the
> >>> build flags default to it.
> >>> I think we should remove this flag, rather than making
> >>> --disable-bind-now work as documented.
> >>
> >> I feel like this needs more thought either way then, no point blocking
> >> 2.38 for it.  What's the use case for lazy binding?  Are people
> >> actually using this in the wild and would we be breaking things for
> >> them?
> > 
> > I don't think it matters.  We have very few symbols that can be bound
> > lazily.  Most symbolic bindings are against data symbols, which cannot
> > be bound lazily, so the performance win for glibc itself is minuscule.
> > 
> > I think it may have been beneficial before we had the libc_hidden
> > mechanism.  I suppose libpthread integration also helped to decreasing
> > binding overhead.
> 
> Fair enough, I'll respin this by dropping the option and let Andreas 
> decide if it's suitable for 2.38.  If not, I'll just queue it up for 2.39.

Let's queue it for 2.39 then.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]