From: Aurelien Jarno <aurelien@aurel32.net>
To: "陳韋任 (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw>
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH] Possible wrong microMIPS opcode encoding
Date: Thu, 15 Nov 2012 14:53:38 +0100 [thread overview]
Message-ID: <20121115135338.GA21046@ohm.aurel32.net> (raw)
In-Reply-To: <20121114235704.GB11985@cs.nctu.edu.tw>
On Thu, Nov 15, 2012 at 07:57:04AM +0800, 陳韋任 (Wei-Ren Chen) wrote:
> On Wed, Nov 14, 2012 at 05:45:21PM +0100, Aurelien Jarno wrote:
> > On Wed, Nov 14, 2012 at 10:49:55AM +0800, 陳韋任 (Wei-Ren Chen) wrote:
> > > Hi all,
> > >
> > > While reading microMIPS decoding, I found a possible wrong opcode
> > > encoding. According to [1] page 337, the bits 13..12 for MULTU is
> > > 0x01 rather than 0x00. Please review, thanks.
> > >
> > > [1] MIPS Architecture for Programmers VolumeIV-e: The MIPS DSP
> > > Application-Specific Extension to the microMIPS32 Architecture
> >
> > This is indeed correct, but I guess the page you meant is 166. Page 337
> > refers to the original MULTU instruction from the MIPS Architecture for
> > Programmers Volume II-B: The microMIPS32 Instruction Set.
> >
> > On the other the microMIPS32 encoding for DSP instruction is not yet
> > supported.
>
> Maybe we can start cleanup it a little bit. ;) Is this OK to commit?
>
My point was that the patch what correct, but not the comment. I have
committed it after fixing the comment.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2012-11-15 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 2:49 [Qemu-trivial] [PATCH] Possible wrong microMIPS opcode encoding 陳韋任 (Wei-Ren Chen)
2012-11-14 5:38 ` Jia Liu
2012-11-14 16:56 ` Aurelien Jarno
2012-11-14 23:51 ` 陳韋任 (Wei-Ren Chen)
2012-11-14 16:45 ` Aurelien Jarno
2012-11-14 23:57 ` 陳韋任 (Wei-Ren Chen)
2012-11-15 13:53 ` Aurelien Jarno [this message]
2012-11-16 1:26 ` 陳韋任 (Wei-Ren Chen)
2012-11-15 1:17 ` 陳韋任 (Wei-Ren Chen)
2012-11-15 13:56 ` Aurelien Jarno
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=20121115135338.GA21046@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=chenwj@iis.sinica.edu.tw \
--cc=qemu-trivial@nongnu.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.