From: Cary Coutant <ccoutant@gmail.com>
To: Alan Modra <amodra@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Michael Matz <matz@suse.de>,
Rich Felker <dalias@libc.org>,
"Carlos O'Donell" <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
nsz@port70.net, Jan Beulich <JBeulich@suse.com>,
Binutils <binutils@sourceware.org>,
gnu-gabi@sourceware.org
Subject: Re: RFC: Add GNU_PROPERTY_NEED_PHDRS
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <CAJimCsETK4udsPG9LYL2Qn5X5nN7NjCbiyuGirUGvgA4MM_qHg@mail.gmail.com> (raw)
In-Reply-To: <20181004021457.GE3179@bubble.grove.modra.org>
> If you specify PHDRS in a script, ld uses exactly those program
> headers, and I believe it should continue to operate that way. So to
> add PT_GNU_EH_FRAME, say, when an executable has .eh_frame_hdr, you'd
> need a script with PT_GNU_EH_FRAME specified in PHDRS. And another
> without PT_GNU_EH_FRAME when the executable doesn't have
> .eh_frame_hdr. That soon becomes impractial considering the number of
> optional headers, requiring auto-generation of the PHDRS script
> snippet.
Oh, I see. Yeah, that does make it impractical.
Still, I'd like to understand why HJ claims it's intrusive to have ld
create a PT_LOAD segment for the headers. I haven't tried it yet in
gold (don't support -z separate-code), but it doesn't seem like it
would be at all difficult or intrusive.
-cary
next prev parent reply other threads:[~2018-10-04 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 H.J. Lu
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` Alan Modra
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` Alan Modra
2018-01-01 0:00 ` Cary Coutant [this message]
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 ` Alan Modra
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=CAJimCsETK4udsPG9LYL2Qn5X5nN7NjCbiyuGirUGvgA4MM_qHg@mail.gmail.com \
--to=ccoutant@gmail.com \
--cc=JBeulich@suse.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=matz@suse.de \
--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).