Re: Difference between --oformat binary, and objcopy -O binary of --oformat elf32-i386

["H.J. Lu" <hjl dot tools at gmail dot com>]

On Tue, Jul 19, 2016 at 6:47 AM, Alan Modra <amodra@gmail.com> wrote:
> On Tue, Jul 19, 2016 at 05:54:38PM +0530, linuxyne citadel wrote:
>> The errors, to which I referred in my previous email, are related to
>> the PIE addressing using GOT.
>
> This is not surprising.  When you use --oformat binary, you're using
> a generic linker backend rather than the x86 specific ELF linker.  The
> generic linker doesn't know how to handle GOT relocs, and a lot of
> other cases.
>
> HJ, it would be nice if x86 implemented something like elf32-ppc.c
> ppc_elf_unhandled_reloc to give an error at link time for all the
> relocs that the generic linker can't handle.
>

I see:

 HOWTO (R_PPC_TLSLD,
         0,                     /* rightshift */
         2,                     /* size (0 = byte, 1 = short, 2 = long) */
         32,                    /* bitsize */
         FALSE,                 /* pc_relative */
         0,                     /* bitpos */
         complain_overflow_dont, /* complain_on_overflow */
         bfd_elf_generic_reloc, /* special_function */
         "R_PPC_TLSLD",         /* name */
         FALSE,                 /* partial_inplace */
         0,                     /* src_mask */
         0,                     /* dst_mask */
         FALSE),                /* pcrel_offset */


Can generic linker handle R_PPC_TLSLD?

-- 
H.J.