From: Cary Coutant <ccoutant@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: nsz@port70.net, JBeulich@suse.com,
"H.J. Lu" <hjl.tools@gmail.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: <CAJimCsG7zNA17K4YP_W8QB=fVVW+msbdXWZh5cVOidN4FGYbWQ@mail.gmail.com> (raw)
In-Reply-To: <874lebtdru.fsf@oldenburg.str.redhat.com>
> * Szabolcs Nagy:
>
> > without containing any sections, however elf says
> > "An object file segment contains one or more sections".
>
> Interesting. This indeed suggests that a covering section for the
> program header is needed, and a new section type for it makes sense.
I would argue that "one or more" is careless wording. It goes on to
say "... though this fact is transparent to the program header.
Whether the file segment holds one or many sections also is immaterial
to program loading."
If you need a special section type just to ensure that the BFD linker
will include the program headers in a loadable segment, that's a mere
implementation detail, and doesn't need to be part of the gABI or
psABI.
-cary
next prev parent reply other threads:[~2018-09-27 22:31 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 ` 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 ` Carlos O'Donell
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
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 ` Michael Matz
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 ` Cary Coutant [this message]
[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='CAJimCsG7zNA17K4YP_W8QB=fVVW+msbdXWZh5cVOidN4FGYbWQ@mail.gmail.com' \
--to=ccoutant@gmail.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=dalias@libc.org \
--cc=fweimer@redhat.com \
--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).