From: Ralf Baechle <ralf@linux-mips.org>
To: Dominic Sweetman <dom@mips.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Linux-MIPS <linux-mips@linux-mips.org>,
Mike Uhler <uhler@mips.com>, "Kevin D. Kissell" <kevink@mips.com>,
Nigel Stephens <nigel@mips.com>
Subject: Re: The MIPS' statement on R_MIPS_PC16 relocations
Date: Fri, 28 Feb 2003 13:57:48 +0100 [thread overview]
Message-ID: <20030228135748.A7285@linux-mips.org> (raw)
In-Reply-To: <15967.10141.166760.373070@arsenal.mips.com>; from dom@mips.com on Fri, Feb 28, 2003 at 09:10:53AM +0000
On Fri, Feb 28, 2003 at 09:10:53AM +0000, Dominic Sweetman wrote:
> The existing definition is nonsense - I won't guess how it happened,
> but there's no reason to keep it. Thiemo has MIPS Technologies'
> thanks and blessing in making this change. Please let our Nigel
> Stephens know when it's done (mailto:nigel@mips.com) and he'll
> double-check it.
>
> I'm sure you'll put comments in the code noting that this is different
> from the document.
>
> There's a more tricky question, which is how we're going to document
> this. I'm currently trying to create a more user-friendly (and
> accurate) ABI document, but had not yet got to the relocation types...
I think for the moment all typo fixed version of the old ABI document would
already be great - and producable at minimal effort.
In the longer run I'd be happy to see the 32-bit and 64-bit ABI documents
unified as it was already happening on www.mipsabi.org when the site and
the MIPS ABI group was shutdown; I think I did save the few bits I was
able to save.
Btw - www.mipsabi.org is on air again. But this time it's a porn site. I
may be tolerant but imho that's really a trademark case for the lawyers.
Ralf
prev parent reply other threads:[~2003-02-28 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.3.96.1030227130833.19733D-100000@delta.ds2.pg.gda.pl>
2003-02-28 9:10 ` The MIPS' statement on R_MIPS_PC16 relocations Dominic Sweetman
2003-02-28 12:57 ` Ralf Baechle [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=20030228135748.A7285@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dom@mips.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=nigel@mips.com \
--cc=uhler@mips.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