Re: glibc 2.36 - Slushy freeze (3 weeks to release)

[Hans-Peter Nilsson <hp@bitrange.com>]

On Tue, 12 Jul 2022, Michael Matz via Binutils wrote:
> Hello,
>
> On Tue, 12 Jul 2022, Florian Weimer wrote:
>
> > > lenient in what you accept", even more so for something so basic as a
> > > program loader.  It seems ill-advised to use ld.so to force something
> > > onto users that can only be called a strive for purity.
> >
> > The problem here is that R_*_NONE has historically been used in binutils
> > to indicate, ?I did not recognize the relocation in the input file?,
> > while still generating an output file.
>
> The usual reason for _NONE are overallocated .rel output sections,
> where then further optimizations (after section sizes and hence base
> addresses are fixed) got rid of some of those relocations.  (All these
> cases can be considered missed optimizations, but those happen easily)
> Unrecognizable input relocations are usually errored out on (and should
> be!) and don't lead to random _NONE output relocs, for exactly the reason
> you cited.

(From the department of opinions nobody asked for:)
This is IMHO the most correct assessment.  And, beware of adding
new potentially relocation-removing linker optimizations after
section layout.  I'd add something about fighting windmills, but
the "strive for purity" fits nicely. :)

brgds, H-P