glibc 2.36 - Slushy freeze (3 weeks to release)

[Alan Modra]

On Tue, Jul 12, 2022 at 08:48:18AM +0800, Xi Ruoyao via Binutils wrote:
> > The R_LARCH_NONE issue should only affect performance,
> > since it should be ignored by loader although I am not sure without
> > understanding better the issue.

R_*_NONE relocs are harmless in an executable or shared library, if
their presence is due to overallocating space for relocations.  Of
course, if ld should actually be emitting some other dynamic reloc
type then that is a more serious problem.

> Fangrui suggested [2] we should assume R_LARCH_NONE does not exist to
> simplify the code and catch ld bugs earlier.

Yes that will annoy your user base into reporting bugs.  How much do
you want to annoy them?  You might like to consider why other major
architectures with mature linkers process and ignore R_*_NONE relocs
in the loader..

-- 
Alan Modra
Australia Development Lab, IBM