NONE Relocations in shared libraries
H.J. Lu
hjl.tools@gmail.com
Tue Nov 17 22:51:09 GMT 2020
On Tue, Nov 17, 2020 at 2:45 PM Michael Morrell via Binutils
<binutils@sourceware.org> wrote:
>
> I sometimes see relocations of type NONE in shared libraries and was wondering what purpose they serve. They seemed to be
> caused by code in a backend relocation function. For example, for x86-64, in elf_x86_64_relocation_section, there is code:
>
> if (skip)
> memset(&outrel, 0, sizeof outrel);
>
> ....
>
> elf_append_rela(output_bfd, sreloc, &outrel);
>
> which appends a relocation with all bytes 0 to the shared library. What is this for?
>
NONE relocation usually is an indication of a backend failing to
accurately account for the number
of dynamic relocations needed. This should be fixed if possible. If
you run into such a case,
please open a binutils bug.
--
H.J.
More information about the Binutils
mailing list