From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Szabolcs Nagy <nsz@port70.net>, Jan Beulich <JBeulich@suse.com>,
Rich Felker <dalias@libc.org>,
Binutils <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: <87va6rqfg6.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOp6bN3Pp4Zc37cfjNKjah00zkzWC-5eEboeJZsbZUkC=g@mail.gmail.com> (H. J. Lu's message of "Thu, 27 Sep 2018 05:37:27 -0700")
* H. J. Lu:
> On Thu, Sep 27, 2018 at 3:35 AM, Szabolcs Nagy <nsz@port70.net> wrote:
>> an alloc .phdr section covering the program headers solves
>> this problem. if sections are not required for segments
>> then simply the linker should ensure that there is always
>> a load segment covering the program headers, possibly
>> without containing any sections, however elf says
>> "An object file segment contains one or more sections".
>>
>> i don't understand why a zero-size section is enough, what
>> if phdr > pagesize? will that get covered by the load
>> segment that is created for the zero-size section?
>
> Linker must keep this zero-size section in output and
> create a PT_LOAD segment to cover it even if it is
> the only SHF_ALLOC section in the PT_LOAD segment.
Based on Szabolcs' comment, I don't think the section can be zero-sized.
Thanks,
Florian
next prev parent reply other threads:[~2018-09-27 12:42 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 ` Florian Weimer
2018-01-01 0:00 ` Jan Beulich
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 [this message]
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
2018-01-01 0:00 ` Carlos O'Donell
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=87va6rqfg6.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=dalias@libc.org \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=nsz@port70.net \
/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).