From: "Prafulla Thakare" <PrafullaT@KPITCummins.com>
To: <binutils@sources.redhat.com>
Cc: "Nick Clifton" <nickc@redhat.com>
Subject: RE: Exploring the possibility of linking objects with different relocationschemes.
Date: Tue, 04 Jan 2005 11:45:00 -0000 [thread overview]
Message-ID: <4A1BE23A7B777442B60F4B4916AE0F1303E8F238@sohm.kpit.com> (raw)
Hi,
We have changed the ABI VERSION in elf header to identify the different
relocation schemes. i.e. ABI = 1 stands for new (binutils 2.15 onwards)
relocations while ABI = 0 stands for old (binutils 2.10) relocations.
In linker, the relocations will be handled based on the ABI version. If
the ABI version is "1", then relocation handling will remain same but
if ABI version is "0", then relocations will be handled the way it is
done in
binutils 2.10.1.
For this purpose, we plan to re-use relocation handling source code of
2.10.1.
Please let us know, if this okay and also if anybody foresee any problem
with this implementation.
Also any input on how above implementation will affect "-r" option to
linker?
>>Can anybody suggest how feasible is to
>> modify present linker to link objects with different relocation
>>scheme at the same time?
>This should be possible. You may find that you cannot support the
>--emit-relocs switch since you would not be able to label the output
>file as containing both old and new ABI relocs.
-->This is okay.
Regards,
Prafulla Thakare
KPIT Cummins InfoSystems Ltd.
Pune, India
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Free download of GNU based tool-chains for Renesas' SH and H8 Series.
The following site also offers free technical support to its users.
Visit http://www.kpitgnutools.com for details.
Latest versions of KPIT GNU tools are released on Oct 1, 2004.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2005-01-04 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 11:45 Prafulla Thakare [this message]
2005-01-05 13:26 ` Nick Clifton
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=4A1BE23A7B777442B60F4B4916AE0F1303E8F238@sohm.kpit.com \
--to=prafullat@kpitcummins.com \
--cc=binutils@sources.redhat.com \
--cc=nickc@redhat.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).