From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xgus2-00051m-RK for qemu-devel@nongnu.org; Wed, 22 Oct 2014 08:18:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xgurx-0000IP-Oh for qemu-devel@nongnu.org; Wed, 22 Oct 2014 08:18:30 -0400 Received: from mailapp01.imgtec.com ([195.59.15.196]:35463) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xgurx-0000I3-Jm for qemu-devel@nongnu.org; Wed, 22 Oct 2014 08:18:25 -0400 Message-ID: <5447A08E.4020900@imgtec.com> Date: Wed, 22 Oct 2014 13:18:22 +0100 From: James Hogan MIME-Version: 1.0 References: <1405331763-57126-1-git-send-email-yongbok.kim@imgtec.com> <1405331763-57126-7-git-send-email-yongbok.kim@imgtec.com> In-Reply-To: <1405331763-57126-7-git-send-email-yongbok.kim@imgtec.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 06/20] target-mips: add MSA opcode enum List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Yongbok Kim , qemu-devel@nongnu.org Cc: cristian.cuna@imgtec.com, leon.alrae@imgtec.com, aurelien@aurel32.net Hi, On 14/07/14 10:55, Yongbok Kim wrote: > @@ -835,6 +839,8 @@ enum { > OPC_BC1 = (0x08 << 21) | OPC_CP1, /* bc */ > OPC_BC1ANY2 = (0x09 << 21) | OPC_CP1, > OPC_BC1ANY4 = (0x0A << 21) | OPC_CP1, > + OPC_MSA_BZ_V = (0x0B << 21) | OPC_CP1, > + OPC_MSA_BNZ_V = (0x0F << 21) | OPC_CP1, I don't think any of the existing secondary opcodes have the ASE prefixed, and the instruction mnemonics should already be unique, so is it worth dropping the MSA_ on these and the other secondary opcodes? > + /* 2R instruction df(bits 17..16) = _b, _h, _w, _d */ > + OPC_MSA_FILL_df = (0x00 << 16) | OPC_MSA_2R, > + OPC_MSA_PCNT_df = (0x04 << 16) | OPC_MSA_2R, > + OPC_MSA_NLOC_df = (0x08 << 16) | OPC_MSA_2R, > + OPC_MSA_NLZC_df = (0x0C << 16) | OPC_MSA_2R, it might be more consistent (and more directly comparable to the encoding table in the manual) to use a shift of 18 here, kind of like you did for the I5 instructions. Same for the 2RF ones below but with a shift of 17. > + > + /* 2RF instruction df(bit 16) = _w, _d */ > + OPC_MSA_FINT_S_df = (0x18 << 16) | OPC_MSA_2RF, > + OPC_MSA_FINT_U_df = (0x1A << 16) | OPC_MSA_2RF, the manual calls these two FTINT rather than FINT Otherwise Reviewed-by: James Hogan Cheers James