From: Yury Gribov <y.gribov@samsung.com>
To: nick clifton <nickc@redhat.com>, Will Newton <will.newton@linaro.org>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
Viacheslav Garbuzov <v.garbuzov@samsung.com>,
Yuri Gribov <tetra2005@gmail.com>
Subject: Re: [RFC][PATCH] Handle arbitrary .plt/.got displacements in ld on ARM
Date: Mon, 24 Feb 2014 15:07:00 -0000 [thread overview]
Message-ID: <530B6043.4070605@samsung.com> (raw)
In-Reply-To: <5307609F.8070001@redhat.com>
Nick Clifton wrote:
> I wonder however whether it would be possible to remove the new command
> line option and have the linker automatically decide between using
> 28-bit or 32-bit PLT entries ?
The problem is that decision on PLT entry size is done long before we
actually output PLT entries.
Fixing this would require a non-trivial code churn which I'm a bit
scared to do...
Note that most of the people are probably ok with existing 28-bit
entries (otherwise we'd know about this issue long ago).
-Y
next prev parent reply other threads:[~2014-02-24 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 10:16 Yury Gribov
2014-02-10 8:32 ` Will Newton
2014-02-10 11:52 ` Yury Gribov
2014-02-17 6:39 ` [PATCH/ARM][PING] " Yury Gribov
2014-02-24 15:09 ` [PATCH/ARM][PING^2] " Yury Gribov
2014-02-21 14:24 ` [RFC][PATCH] " nick clifton
2014-02-24 15:07 ` Yury Gribov [this message]
2014-02-25 9:02 ` nick clifton
2014-02-27 12:53 ` Yury Gribov
2014-02-27 14:42 ` nick clifton
2014-02-28 5:53 ` Hans-Peter Nilsson
2014-02-28 6:15 ` Yury Gribov
2014-02-28 19:40 ` Hans-Peter Nilsson
2014-02-28 19:57 ` Yuri Gribov
2014-03-01 11:27 ` Hans-Peter Nilsson
2014-03-02 16:10 ` Nicholas Clifton
2014-02-25 16:46 ` Richard Earnshaw
2014-02-25 18:01 ` Yuri Gribov
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=530B6043.4070605@samsung.com \
--to=y.gribov@samsung.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=tetra2005@gmail.com \
--cc=v.garbuzov@samsung.com \
--cc=will.newton@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).