From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Project Revolution <projectrevotpp@hotmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"kenixwhisperwind@gmail.com" <kenixwhisperwind@gmail.com>
Subject: Re: GCC generates non-compliant MIPS relocation data? Obscure GNU extension?
Date: Sun, 28 Feb 2021 01:36:31 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2102280126370.44210@angie.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2102191835480.2021@angie.orcam.me.uk>
On Fri, 19 Feb 2021, Maciej W. Rozycki wrote:
> It looks to me however that you actually have control over the relocation
> processing code you have referred, so how about improving it to handle the
> GNU R_MIPS_HI16 extension as well?
FWIW note that the extension has been around for ~25 years now (which I
forgot to mention previously).
Maciej
prev parent reply other threads:[~2021-02-28 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 19:57 Project Revolution
2021-02-18 20:28 ` Andrew Pinski
2021-02-18 21:20 ` Project Revolution
2021-02-19 0:54 ` Project Revolution
2021-02-19 18:17 ` Maciej W. Rozycki
2021-02-28 0:36 ` Maciej W. Rozycki [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=alpine.DEB.2.21.2102280126370.44210@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=gcc@gcc.gnu.org \
--cc=kenixwhisperwind@gmail.com \
--cc=projectrevotpp@hotmail.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).