From: Michael Uhler <uhler@mips.com>
To: Mark and Janice Juszczec <juszczec@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: r3000 instruction set
Date: 21 Feb 2004 19:15:49 -0800 [thread overview]
Message-ID: <1077419749.27294.2.camel@gmu-linux> (raw)
In-Reply-To: <Law10-F39hgbi1Kigvf000046ac@hotmail.com>
Unfortunately, what you want isn't the r3000 instruction list but,
instead the 3912 instruction list. While the original r3000
instructions were well-defined, each manufacturer tended to
add or subtract certain instructions in each implementation
(creating the kind of behavior and questions that you're seeing).
So rather than asking for the list, why not just post the disassembly
and the pc of the reserved instruction?
/gmu
On Sat, 2004-02-21 at 19:02, Mark and Janice Juszczec wrote:
> Hi folks
>
> I'm working with kaffe on a r3912 cpu. I'm getting an illegal instruction
> error. I disassembled the kaffe binary and thought I'd find the offending
> instruction.
>
> Unfortunately, I found 2 different lists of r3000 assembler instructions at:
>
> http://www.xs4all.nl/~vhouten/mipsel/r3000-isa.html
> http://www.xs4all.nl/~vhouten/mipsel/appB.html
>
> and comparing them against the list of disassembled kaffe instructions
> gives 2 different results.
>
> So, can someone recommend a definitive list of r3000 assembler instructions?
>
> Any help would be greatly appreciated.
>
> Mark
>
> _________________________________________________________________
> Find and compare great deals on Broadband access at the MSN High-Speed
> Marketplace. http://click.atdmt.com/AVE/go/onm00200360ave/direct/01/
>
>
--
Michael Uhler, Chief Technology Officer
MIPS Technologies, Inc. Email: uhler@mips.com
1225 Charleston Road Voice: (650)567-5025 FAX: (650)567-5225
Mountain View, CA 94043 Mobile: (650)868-6870 Admin: (650)567-5085
next prev parent reply other threads:[~2004-02-22 3:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 3:02 r3000 instruction set Mark and Janice Juszczec
2004-02-22 3:15 ` Michael Uhler [this message]
2004-02-22 9:32 ` Kevin D. Kissell
2004-02-22 9:32 ` Kevin D. Kissell
2004-02-22 12:31 ` Dominic Sweetman
2004-02-22 19:13 ` Eric Christopher
2004-02-22 21:52 ` Kevin D. Kissell
2004-02-22 21:52 ` Kevin D. Kissell
2004-02-23 3:03 ` Steven J. Hill
2004-02-23 7:03 ` Kevin D. Kissell
2004-02-23 7:03 ` Kevin D. Kissell
2004-02-23 3:37 ` Eric Christopher
2004-02-23 7:11 ` Kevin D. Kissell
2004-02-23 7:11 ` Kevin D. Kissell
2004-02-23 7:29 ` Eric Christopher
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 16:56 Mark and Janice Juszczec
2004-02-23 17:07 ` Michael Uhler
2004-02-23 17:13 ` Maciej W. Rozycki
2004-02-23 17:21 ` Kevin D. Kissell
2004-02-23 17:21 ` Kevin D. Kissell
2004-02-23 17:59 ` Dominic Sweetman
2004-02-23 20:48 Mark and Janice Juszczec
2004-02-23 22:46 ` Kevin D. Kissell
2004-02-23 22:46 ` Kevin D. Kissell
2004-03-01 15:38 Mark and Janice Juszczec
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=1077419749.27294.2.camel@gmu-linux \
--to=uhler@mips.com \
--cc=juszczec@hotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.