From: Rich Felker <dalias@libc.org>
To: linux-sh@vger.kernel.org
Subject: Re: SH FDPIC ABI spec/binutils and kernel conflict on flag definitions
Date: Thu, 10 Sep 2015 16:01:49 +0000 [thread overview]
Message-ID: <20150910160149.GP17773@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150910033400.GM17773@brightrain.aerifal.cx>
On Thu, Sep 10, 2015 at 04:53:35PM +0100, David Howells wrote:
> Rich Felker <dalias@libc.org> wrote:
>
> > On the other hand, the only existing way to produce a binary that both
> > (1) needs constant displacement, and (2) actually gets constant
> > displacement from the kernel at load time, is to manually edit the ELF
> > headers to flip the bit. So I really doubt any such binaries exist. Do
> > you have a reason to believe they do?
>
> Well, Fujitsu asked for it for FRV - I've no idea whether they have such
> binaries still.
OK. Can we get feedback from anyone who's actually using this code
now? I don't see how the current situation is at all acceptable for
anyone using it, but maybe I'm missing something. It seems programs
built as FDPIC are going through all the ABI cost for FDPIC (function
descriptors, restricted relative addressing) for absolutely no gain
because the kernel just loads them like plain non-FDPIC ELF files...
Rich
next prev parent reply other threads:[~2015-09-10 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 3:34 SH FDPIC ABI spec/binutils and kernel conflict on flag definitions Rich Felker
2015-09-10 11:57 ` Nick Clifton
2015-09-10 14:58 ` Rich Felker
2015-09-10 15:45 ` David Howells
2015-09-10 15:50 ` Rich Felker
2015-09-10 15:53 ` David Howells
2015-09-10 16:01 ` Rich Felker [this message]
2015-09-10 21:09 ` Rich Felker
2015-09-14 16:09 ` Rich Felker
2015-12-30 3:55 ` Mike Frysinger
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=20150910160149.GP17773@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=linux-sh@vger.kernel.org \
/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 NNTP newsgroup(s).