From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Jakub Jelinek <jakub@redhat.com>,
Jan Beulich <JBeulich@novell.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
GCC Development <gcc@gcc.gnu.org>,
x32-abi@googlegroups.com, Binutils <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: x32 psABI draft version 0.2
Date: Thu, 17 Feb 2011 18:14:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1102171807480.31965@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20110217152233.GB11346@atrey.karlin.mff.cuni.cz>
On Thu, 17 Feb 2011, Jan Hubicka wrote:
> > REL is horrible pain, we shouldn't ever add new REL targets.
>
> According to Mozilla folks however REL+RELA scheme used by EABI leads
> to significandly smaller libxul.so size
>
> According to http://glandium.org/blog/?p=1177 the difference is about 4-5MB
> (out of approximately 20-30MB shared lib)
Well - as noted there, while EABI supports both, binutils just uses REL on
ARM (except for VxWorks, where it uses RELA). Supporting both
simultaneously - linking a mixture of objects with the two types, possibly
with both mixed within a single object - is much more of a pain (at least
for the BFD linker, I don't know about gold) than simply supporting one or
the other for a single ABI - it's required by ARM EABI, but that bit of
EABI isn't actually supported by binutils. I think most of the
target-independent BFD problems with mixing REL and RELA have been ironed
out by now in the course of Bernd's work on linking objects from TI's C6X
tools, but it also needs care in the target-specific BFD code (you always
need to check for each individual relocation what sort it is, rather than
checking any global flag).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2011-02-17 18:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 19:22 H.J. Lu
2011-02-16 20:04 ` H. Peter Anvin
2011-02-16 20:29 ` Roland McGrath
2011-02-16 20:35 ` Chris Metcalf
2011-02-16 20:39 ` Andrew Pinski
2011-02-16 20:46 ` H.J. Lu
2011-02-16 22:13 ` Chris Metcalf
2011-02-17 8:35 ` Jan Beulich
2011-02-17 12:14 ` H.J. Lu
2011-02-17 16:14 ` John Reiser
2011-02-17 17:59 ` Jakub Jelinek
2011-02-17 14:29 ` Jakub Jelinek
2011-02-17 15:22 ` Jan Hubicka
2011-02-17 15:30 ` H.J. Lu
2011-02-17 15:45 ` Jan Hubicka
2011-02-17 15:49 ` H.J. Lu
2011-02-17 16:10 ` Jan Beulich
2011-02-17 17:59 ` H.J. Lu
2011-02-18 8:10 ` Jan Beulich
2011-02-18 17:53 ` H.J. Lu
2011-02-18 20:32 ` Jan Hubicka
2011-02-21 8:04 ` Jan Beulich
2011-02-17 18:07 ` Jakub Jelinek
2011-02-17 19:56 ` H. Peter Anvin
2011-02-17 22:50 ` Jan Hubicka
2011-02-17 23:00 ` H. Peter Anvin
2011-02-17 23:07 ` Jakub Jelinek
2011-02-18 8:49 ` Jan Beulich
2011-02-17 18:14 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1102171807480.31965@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=JBeulich@novell.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=x32-abi@googlegroups.com \
/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).