public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org,  Kaylee Blake <klkblake@gmail.com>
Subject: Re: RFC: [PATCH] ELF: Don't require section header on ELF objects
Date: Mon, 09 Mar 2020 09:13:16 +0100	[thread overview]
Message-ID: <87y2sac5er.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20200308175947.GA911529@gmail.com> (H. J. Lu's message of "Sun,  8 Mar 2020 10:59:47 -0700")

* H. J. Lu:

> Section header isn't mandatory on ELF executable nor shared library.
> This patch adds a new linker option, -z nosectionheader, to omit ELF
> section header when building an executable or shared library, adds
> an objcopy and strip option, --remove-section-header, to remove ELF
> section header from an executable or shared library.
>
> The PT_DYNAMIC segment contains DT_HASH/DT_GNU_HASH/DT_MIPS_XHASH,
> DT_STRTAB, DT_SYMTAB, DT_STRSZ and DT_SYMENT, which can be used to
> reconstruct dynamic symbol table when section header isn't available.
> For DT_HASH, the number of dynamic symbol table entries equals the
> number of chains.  For DT_GNU_HASH/DT_MIPS_XHASH, only defined symbols
> with non-STB_LOCAL indings are in hash table.  Since in dynamic symbol
> table, all symbols with STB_LOCAL binding are placed before symbols with
> other bindings and all defined symbols are placed before undefined ones,
> the highest symbol index in DT_GNU_HASH/DT_MIPS_XHASH is the highest
> dynamic symbol table index.

Does this patch enable ld to use shared objects without a section
header for linking?

I think the NEWS and manual update should clarify this.

In my opinion, it should NOT be possible to link against objects
without section headers.  Lack of section headers clearly marks the
object as a run-time only object.  This is useful if you want to
prevent developers to create DT_NEEDED dependencies on internal
libraries, for example.

  parent reply	other threads:[~2020-03-09  8:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08 17:59 H.J. Lu
2020-03-08 18:06 ` H.J. Lu
2020-03-08 23:35   ` Alan Modra
2020-03-08 23:46     ` H.J. Lu
2020-03-09  0:02       ` H.J. Lu
2020-03-09  0:02       ` Kaylee Blake
2020-03-09  0:05       ` Alan Modra
2020-03-09  1:36         ` H.J. Lu
2020-03-09  1:59           ` Kaylee Blake
2020-03-09  2:23             ` Alan Modra
2020-03-09  2:35               ` H.J. Lu
2020-03-09  4:14                 ` H.J. Lu
2020-03-09  4:59                   ` Kaylee Blake
2020-03-09 11:56                 ` Alan Modra
2020-03-08 23:24 ` Kaylee Blake
2020-03-08 23:29   ` H.J. Lu
2020-03-08 23:38     ` Alan Modra
2020-03-08 23:45       ` H.J. Lu
2020-03-12  2:14         ` Fangrui Song
2020-03-09  8:13 ` Florian Weimer [this message]
2020-03-09 12:54   ` Kaylee Blake
2020-03-09 13:06     ` Florian Weimer
2020-03-09 13:14       ` Kaylee Blake
2020-03-09 13:16         ` Florian Weimer
2020-03-09 13:28           ` Kaylee Blake
2020-03-09 13:29             ` Florian Weimer
2020-03-09 13:45               ` Kaylee Blake
2020-03-09 13:54                 ` H.J. Lu
2020-03-09 14:02                   ` Kaylee Blake
2020-03-09 14:52                 ` Florian Weimer
2020-03-09 15:07                   ` Kaylee Blake
2020-03-09 15:29                     ` Florian Weimer
2020-03-09 13:44     ` Alan Modra
2020-03-09 13:54       ` Kaylee Blake
2020-03-09 22:34         ` Alan Modra
2020-03-10  0:14           ` H.J. Lu
2020-03-09 14:34       ` Michael Matz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2sac5er.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=klkblake@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).