public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Jeff Baker <jbaker@qnx.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Handle mtsprg and mfsprg properly for BookE
Date: Wed, 09 Mar 2005 02:11:00 -0000	[thread overview]
Message-ID: <20050309021118.GJ15642@bubble.modra.org> (raw)
In-Reply-To: <422E4F55.2060904@qnx.com>

On Tue, Mar 08, 2005 at 08:20:21PM -0500, Jeff Baker wrote:
> Would it be correct to change the generic PPC_OPCODE_BOOKE case to 
> always use user mode sprg2+ and then override it to be sprg3+ for 
> PPC_OPCODE_403 and PPC_OPCODE_440?  Should there be a version of mtsprg3 
> for e500 and MPC8560 that encodes 259 instead of 275?

That's what _you_ need to research.  If you can decide on the correct
mapping of sprg number to spr number for a given processor, and defend
your mapping against potential criticism, I'm more than happy to help
correct an implementation.

Hmm, looking over your patch again, I suppose you could simply say that
your mapping of sprg number to spr number matches the existing gas
opcodes.  ie.  "mfsprg 0,4" generates the same as "mfsprg4 0" and so on.
Enumerate all the possibilities in an addition to the testsuite, and
you've made that obvious.  If you fix the formatting, correct the error
messages, and extend the testsuite this way I'll accept the patch.  I'll
also still be worried that gas isn't generating the right opcodes, but
I suppose that's another issue..

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2005-03-09  2:11 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 [this message]
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
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=20050309021118.GJ15642@bubble.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sourceware.org \
    --cc=jbaker@qnx.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).