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 relocation schemes.
Date: Thu, 16 Dec 2004 11:59:00 -0000 [thread overview]
Message-ID: <41C179F8.7070800@redhat.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1303B6AF81@sohm.kpit.com>
Hi Prafulla,
> Solution as per our understanding:
> We will Change the ABI number in the object file to indicate the
> relocation scheme used.
This is the correct approach.
> Also we are exploring the possibility of linking objects with different
> relocation schemes together. 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.
Cheers
Nick
prev parent reply other threads:[~2004-12-16 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 5:42 Prafulla Thakare
2004-12-16 11:59 ` 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=41C179F8.7070800@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).