From: Ralf Baechle <ralf@linux-mips.org>
To: Paul_Koning@Dell.com
Cc: binutils@sourceware.org, linux-mips@linux-mips.org, dvdkhlng@gmx.de
Subject: Re: $ta0 .. $ta3 registers in O32 on MIPS
Date: Wed, 28 Sep 2011 21:43:20 +0200 [thread overview]
Message-ID: <20110928194319.GA17409@linux-mips.org> (raw)
In-Reply-To: <09787EF419216C41A903FD14EE5506DD030987ABAE@AUSX7MCPC103.AMER.DELL.COM>
On Wed, Sep 28, 2011 at 10:11:40AM -0500, Paul_Koning@Dell.com wrote:
> >I was expecting an error message and I'm wondering, was this intentional?
>
> I would say so. I call this a feature. It makes it easier to write assembly code that assembles without change in both O32 and N32/N64. Consider a function that has 4 or fewer arguments, but needs a pile of scratch registers. It can use ta0-ta3 as four scratch registers, which is correct in all the ABIs.
Turns out that later IRIX version also retroactively introduced the
ta registers for O32 and I just never noticed. So I'm going to change the
Linux kernel headers for consistence and compatibility with everybody else.
Ralf
prev parent reply other threads:[~2011-09-28 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 12:33 $ta0 .. $ta3 registers in O32 on MIPS Ralf Baechle
2011-09-28 15:11 ` Paul_Koning
2011-09-28 15:11 ` Paul_Koning
2011-09-28 19:43 ` 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=20110928194319.GA17409@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Paul_Koning@Dell.com \
--cc=binutils@sourceware.org \
--cc=dvdkhlng@gmx.de \
--cc=linux-mips@linux-mips.org \
/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