From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60895) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fxbUf-0002N2-AB for qemu-devel@nongnu.org; Wed, 05 Sep 2018 13:21:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fxbUa-0007y8-BE for qemu-devel@nongnu.org; Wed, 05 Sep 2018 13:21:29 -0400 Received: from mail-eopbgr680131.outbound.protection.outlook.com ([40.107.68.131]:53068 helo=NAM04-BN3-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fxbUZ-0007tx-SI for qemu-devel@nongnu.org; Wed, 05 Sep 2018 13:21:24 -0400 From: Aleksandar Markovic Date: Wed, 5 Sep 2018 17:21:21 +0000 Message-ID: References: <20180830193019.20104-1-jancraig@amazon.com>, <20180830193019.20104-4-jancraig@amazon.com> , <1a16b26ca5234092b9a5d60082881a15@EX13D12UEA003.ant.amazon.com> In-Reply-To: <1a16b26ca5234092b9a5d60082881a15@EX13D12UEA003.ant.amazon.com> Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH v4 3/9] target/mips: Split mips instruction handling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Janeczek, Craig" , "qemu-devel@nongnu.org" Cc: "aurelien@aurel32.net" , Petar Jovanovic , Richard Henderson > From: Janeczek, Craig > Sent: Tuesday, September 4, 2018 4:44 PM > > Subject: RE: [PATCH v4 3/9] target/mips: Split mips instruction handling > > To clarify the OPC_MUL here is not an MXU instruction, this is the origin= al OPC_MUL that was in the special2 instruction set. The inclusion of this = instruction in this switch statement is due to the suggested method of spli= tting up the mxu commands instruction handling switch statement from the or= iginal special2 commands. There are five more cases where current SPECIAL2 instructions occupy free s= lots in MXU opcode scheme: /* Loongson 2F */ OPC_MODU_G_2F =3D 0x1e | OPC_SPECIAL2, OPC_DMODU_G_2F =3D 0x1f | OPC_SPECIAL2, /* Misc */ OPC_CLZ =3D 0x20 | OPC_SPECIAL2, OPC_CLO =3D 0x21 | OPC_SPECIAL2, /* Special */ OPC_SDBBP =3D 0x3F | OPC_SPECIAL2, What to do with them? Should they be treated like OPC_MUL? Can you do the s= ame binary check as for OPC_MUL? Is there a confirmation in Ingenic gcc/asm= source for all these cases? Thanks, Aleksandar=