From: Nick Clifton <nickc@redhat.com>
To: Prafulla Thakare <PrafullaT@KPITCummins.com>
Cc: binutils@sources.redhat.com
Subject: Re: Exploring the possibility of linking objects with different relocationschemes.
Date: Wed, 05 Jan 2005 13:26:00 -0000 [thread overview]
Message-ID: <41DBECBC.3@redhat.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1303E8F238@sohm.kpit.com>
Hi Prafulla,
> 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.
Note - you should probably define constants for these values and put
them into include/elf/sh.h.
> Please let us know, if this okay and also if anybody foresee any problem
This is OK.
> Also any input on how above implementation will affect "-r" option to
> linker?
It should not be a problem. As long as the code correctly propagates
the ABIVERSION value to the output bfd (which should happen
automatically, you should not need to add any new code).
Cheers
Nick
prev parent reply other threads:[~2005-01-05 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 11:45 Prafulla Thakare
2005-01-05 13:26 ` Nick Clifton [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=41DBECBC.3@redhat.com \
--to=nickc@redhat.com \
--cc=PrafullaT@KPITCummins.com \
--cc=binutils@sources.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).