From: "Amarnath" <amarnath@acmet.com>
To: "'BinutilsAtRedhat'" <binutils@sources.redhat.com>
Subject: [Query] : Usage of single LO relocation
Date: Fri, 21 Apr 2006 14:55:00 -0000 [thread overview]
Message-ID: <003801c6652b$ad7b0ec0$ad00a8c0@amarnath> (raw)
As per my previous query results, I have observed that we should have HI
relocation and LO relocation immediately following each other.
With that as reference, a new query has been raised for me. Please check
it.
Query 1
-------
If we have multiple LO relocations emitted for a single HI relocation as
following patterns, will the second LO relocation be utilized for any
purpose by the GCC linker?
Pattern
-------
R_MIPS_HI16
R_MIPS_LO16
R_MIPS_LO16 <-- Will linker utilize it for some relocations?
Query 2
-------
As I have examined, I have not yet found any usage of LO relocation as a
separate one. Can we have usage of LO relocation without HI relocation
in any case?
Please clarify it.
Regards,
Amarnath M
next reply other threads:[~2006-04-21 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 14:55 Amarnath [this message]
2006-04-21 17:42 ` Thiemo Seufer
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='003801c6652b$ad7b0ec0$ad00a8c0@amarnath' \
--to=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).