From: Toshi Morita <tm2@best.com>
To: bfd@sourceware.cygnus.com
Subject: Re: arm questions
Date: Fri, 16 Apr 1999 03:21:00 -0000 [thread overview]
Message-ID: <199904161021.DAA19183@shell14.ba.best.com> (raw)
In-Reply-To: <3.0.5.32.19990416083918.0099b8a0@mail1.bateman.arm.com>
> >In fact as far as Linux is concerned it probably wouldn't be an especially
> >big deal to introduce RELA in parallel with REL if we wanted to. I think
> >there were rumblings that the ARM SDT compiler was primarily using RELA,
>
> No. ARM only uses REL. We see no advantage to RELA. However, our ELF
> linker (not yet released) handles RELA or any mix of REL and RELA
> (as the ELF standard seems to intend).
>
> AFAIK, Green Hills uses RELA only in its ARM ELF tool chain.
>
> >so we
> >might end up doing it in order to be able to interwork with them. Our
> dynamic
> >linker can be taught to handle binaries with an arbitrary mix of reloc
> types,
> >I think, and I imagine binutils can be made to handle this too if it doesn't
> >already.
The BFD when configured for sh-elf supports both REL and RELA relocation types
although sh-elf-gcc itself only uses REL.
Toshi
next prev parent reply other threads:[~1999-04-16 3:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-15 10:38 Doug Evans
1999-04-15 11:01 ` Ian Lance Taylor
1999-04-15 11:31 ` Scott Bambrough
1999-04-15 11:47 ` Ian Lance Taylor
1999-04-15 13:29 ` H.J. Lu
1999-04-15 13:59 ` Ian Lance Taylor
1999-04-15 14:15 ` Mixing REL and RELA H.J. Lu
1999-04-15 14:21 ` Ian Lance Taylor
1999-04-15 14:28 ` H.J. Lu
1999-04-15 13:10 ` arm questions H.J. Lu
1999-04-15 13:45 ` Ian Lance Taylor
1999-04-15 13:36 ` Philip Blundell
1999-04-16 0:43 ` Lee Smith
1999-04-16 3:21 ` Toshi Morita [this message]
[not found] ` <3.0.5.32.19990416083918.0099b8a0.cygnus.local.bfd@mail1.bateman.arm.com>
1999-04-18 17:10 ` Doug Evans
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=199904161021.DAA19183@shell14.ba.best.com \
--to=tm2@best.com \
--cc=bfd@sourceware.cygnus.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).