public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: joel@merlin.gcs.redstone.army.mil
Cc: gas2@cygnus.com
Subject: Re: PowerPC Instructions
Date: Fri, 01 Dec 1995 13:56:00 -0000	[thread overview]
Message-ID: <199512012156.QAA17270@sanguine.cygnus.com> (raw)
In-Reply-To: <Pine.SV4.3.91.951201151523.10603G-100000@merlin>

   Date: Fri, 1 Dec 1995 15:19:15 -0600 (CST)
   From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>

   I have a user submitted port of RTEMS to the PowerPC (IBM 403) and it uses
   some instructions (or alternate names) he added to his local gas.  I am
   using binutils 2.6 configured for powerpc-elf.  I know of the following
   based on the error messages: 

   /usr1/tmp/cca004pL.s: Assembler messages:
   /usr1/tmp/cca004pL.s:54: Error: Unrecognized opcode: `mtsprg3'
   /usr1/tmp/cca004pL.s:56: Error: Unrecognized opcode: `mtsprg2'
   /usr1/tmp/cca004pL.s:131: Error: Unrecognized opcode: `mtexier'
   /usr1/tmp/cca004pL.s:137: Error: Unrecognized opcode: `mttsr'
   /usr1/tmp/cca004pL.s:143: Error: Unrecognized opcode: `mttsr'

These are all ``move to special register'' instructions.  If you can
find out the appropriate special register number, it should be
possible to replace them all with the mtspr instruction.

Incidentally, gas already supports mtsprg with two operands.  I don't
know what the other two are.

If these are standard instructions for the 403, then you should patch
opcodes/ppc-opc.c and send in the patch.  Look for mtmq to see the
mtspr variants.

Ian


      reply	other threads:[~1995-12-01 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-01 13:47 Joel Sherrill
1995-12-01 13:56 ` Ian Lance Taylor [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=199512012156.QAA17270@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=joel@merlin.gcs.redstone.army.mil \
    /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).