From: "Jan Beulich" <JBeulich@suse.com>
To: "Florian Weimer" <fweimer@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,<binutils@sourceware.org>,
<gnu-gabi@sourceware.org>
Subject: Re: RFC: Add SHT_GNU_PHDRS
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <5BAC7D6802000078001EC6D1@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <87tvmbv8hp.fsf@oldenburg.str.redhat.com>
>>> On 27.09.18 at 07:01, <fweimer@redhat.com> wrote:
> * H. J. Lu:
>
>> I am proposing
>>
>> #define SHT_GNU_PHDRS 0x6ffffff4 /* Dummy section for program header */
>>
>> This is a special read-only SHF_ALLOC zero-size data section. It is the
>> first output section, which will force a data PT_LOAD segment with program
>> header before the code-only PT_LOAD segment,
>
> Is it actually a requirement in the ELF specification that all bits
> loaded via segments are covered by sections as well?
Hardly, because the presence of a section table isn't required
in the first place in an executable (iirc).
Jan
next prev parent reply other threads:[~2018-09-27 6:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 H.J. Lu
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Jan Beulich [this message]
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Szabolcs Nagy
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Rich Felker
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Carlos O'Donell
[not found] ` <CAORpzuOWtHeqBLEE+MMN4-TZyp6Z1r-MdmyNv7Zj-BhxMstr=g@mail.gmail.com>
2018-01-01 0:00 ` H.J. Lu
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=5BAC7D6802000078001EC6D1@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@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).