From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] Update relocation values for ARC platform.
Date: Mon, 25 Apr 2005 10:54:00 -0000 [thread overview]
Message-ID: <426CC8E3.3030906@codito.com> (raw)
In-Reply-To: <426CB82C.8010008@redhat.com>
Hi Nick,
>> This patch corrects the values of the relocation types for
>> the ARC platform. Tested by building cross arc-elf32 and running the
>> tests with no regressions.
>
>
> I am worried about this. What has happened to the old relocation values
> (1, 2, 3) ? What about backwards compatibility ?
FSF mainline was not ABI compliant with respect to these
relocation values. (The relocation values 1, 2 and 3 are
actually reserved for the relocation types R_ARC_8,
R_ARC_16, R_ARC_24. ostensibly generated by the other
toolchain for the ARC cores. ) which the GNU tools does not
generate / handle currently.Mainline seems to have the
values of 1,2,3 for these relocation types since the first
revision.
With respect to backwards compatibility, if anything this
should enable users to link in GNU compiled binaries with
the other propreitary toolchain with a few more patches that
are still in my pipeline. A persistent complaint has been
this inability to link object files generated by the 2
toolsets for the ARC platform .
Would a NEWS item indicating this change be a valid thing
to do indicating that mainline would be broken w.r.t 2.16
branch. ? Or would you want to put in some sort of version
checks in the linker based on version info emitted by the
assembler ?
cheers
Ramana
---
Ramana Radhakrishnan
GNU Tools
codito ergo sum (www.codito.com)
next prev parent reply other threads:[~2005-04-25 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 9:15 Ramana Radhakrishnan
2005-04-25 9:29 ` Nick Clifton
2005-04-25 10:54 ` Ramana Radhakrishnan [this message]
2005-04-25 13:15 ` Nick Clifton
2005-04-27 10:42 ` Ramana Radhakrishnan
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=426CC8E3.3030906@codito.com \
--to=ramana.radhakrishnan@codito.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).