From: Thiemo Seufer <ths@networkno.de>
To: Amarnath <amarnath@acmet.com>
Cc: binutils@sources.redhat.com
Subject: Re: Query in MIPS HI and LO relocations
Date: Thu, 20 Apr 2006 15:24:00 -0000 [thread overview]
Message-ID: <20060420143137.GC10665@networkno.de> (raw)
In-Reply-To: <000201c66486$d17663b0$ad00a8c0@amarnath>
Amarnath wrote:
> Hi all,
>
> I am having a query in the MIPS ABI. As per the SYSTEM V ABI,
> R_MIPS_HI16 relocation should be immediately followed by its
> corresponding R_MIPS_LO16.
The ELF ABI specifies this requirement. The GNU toolchain supports
somewhat relaxed rules which allow some optimisations.
> I would like to know whether this is specific to SYSTEM V architecture
> alone / the linker specification can be changed as per our own
> architecture.
Well, you can change it to anything you like, but it likely won't
be compatible any more. :-)
I recommend you stick with the model the GNU toolchain implements.
Thiemo
next prev parent reply other threads:[~2006-04-20 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 14:50 Amarnath
2006-04-20 15:24 ` Thiemo Seufer [this message]
2006-04-20 15:36 ` Eric Christopher
2006-04-20 16:00 ` Dave Korn
2006-04-21 10:06 ` Amarnath
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=20060420143137.GC10665@networkno.de \
--to=ths@networkno.de \
--cc=amarnath@acmet.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).