From: Alan Modra <amodra@bigpond.net.au>
To: binutils@sources.redhat.com
Cc: Alex Rosenberg <alexr@leftfield.org>, Jeff Baker <jbaker@qnx.com>,
Kumar Gala <kumar.gala@freescale.com>
Subject: Re: [PATCH] Handle mtsprg and mfsprg properly for BookE
Date: Mon, 14 Mar 2005 04:14:00 -0000 [thread overview]
Message-ID: <20050314041420.GJ13506@bubble.modra.org> (raw)
In-Reply-To: <ad80a57d7a545e4541f6fbaa2178ad4c@leftfield.org>
On Sun, Mar 13, 2005 at 03:34:33PM -0800, Alex Rosenberg wrote:
> On Mar 9, 2005, at 7:58 PM, Alan Modra wrote:
> >There remains the question of which spr number should be used by
> >privileged programs for read access to sprg4 through sprg7. Does the
> >non-privileged spr number work when privileged? I would think it
> >probably does, but I'm just guessing..
>
> I think the documentation is the problem here.
>
> Originally, the user mode read-only SPRG were supposed to be referred
> to as USPRG.
Makes sense. Consistent with the spr numbering for USPRG0 too.
I propose that gas adopt this syntax. ie.
mtsprg and mtsprg[0-7] writes spr272..279 (as we currently do)
mfsprg and mfsprg[0-7] read the same regs as mtsprg
mfusprg0 reads spr256 (as we currently do)
Add new mfusprg[3-7] insns which read spr259..263
Add a new mfusprg insn which reads spr256..263
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-03-14 4:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 20:20 Jeff Baker
2005-02-28 21:11 ` Jeff Baker
2005-02-28 21:26 ` Kumar Gala
2005-02-28 22:52 ` Jeff Baker
2005-02-28 23:09 ` Jeff Baker
2005-03-07 15:22 ` Jeff Baker
2005-03-08 11:20 ` Alan Modra
2005-03-08 16:30 ` Jeff Baker
2005-03-08 23:51 ` Alan Modra
2005-03-09 1:18 ` Jeff Baker
2005-03-09 2:11 ` Alan Modra
2005-03-09 16:39 ` Jeff Baker
2005-03-10 12:42 ` Alan Modra
2005-03-09 22:30 ` Kumar Gala
2005-03-10 3:58 ` Alan Modra
[not found] ` <ad80a57d7a545e4541f6fbaa2178ad4c@leftfield.org>
2005-03-14 4:14 ` Alan Modra [this message]
2005-03-16 16:39 ` Jeff Baker
2005-03-17 15:36 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2005-02-24 0:32 Jeff Baker
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=20050314041420.GJ13506@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=alexr@leftfield.org \
--cc=binutils@sources.redhat.com \
--cc=jbaker@qnx.com \
--cc=kumar.gala@freescale.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).