From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailbox.box.xen0n.name (mail.xen0n.name [115.28.160.31]) by sourceware.org (Postfix) with ESMTPS id 9F422385800A for ; Fri, 30 Jun 2023 03:52:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9F422385800A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=xen0n.name Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=xen0n.name DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xen0n.name; s=mail; t=1688097133; bh=EYjwiySDT8C1EYM3sDzdGa0tD5Iwt1iQHaG0ZjRuUZs=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=f7U76f3z5NnUQW1F0SmT5nDjBbV33pkqLoGZ44dwdzACZoS+eVTXi6vz8h7I4VABy D39GxVTfNEikkddursjMB4n5vfPwm2S3RGZJtB7ilTi4F6cQFC0FczQcaOJqGP27iy pHk4F9mHCjAAqk6ehWhgBJDGEKt41U0BSrCgQy6k= Received: from [192.168.9.172] (unknown [101.88.25.181]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailbox.box.xen0n.name (Postfix) with ESMTPSA id 01F5D600BD; Fri, 30 Jun 2023 11:52:12 +0800 (CST) Message-ID: <78c011c2-679c-3b01-ab75-e1d59d79cf88@xen0n.name> Date: Fri, 30 Jun 2023 11:52:11 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH v1 1/2] LoongArch: gas: Add LVZ and LBT instructions support Content-Language: en-US To: mengqinggang , binutils@sourceware.org Cc: xuchenghua@loongson.cn, chenglulu@loongson.cn, liuzhensong@loongson.cn, xry111@xry111.site, i.swmail@xen0n.name, maskray@google.com References: <20230630033443.2359278-1-mengqinggang@loongson.cn> <20230630033443.2359278-2-mengqinggang@loongson.cn> From: WANG Xuerui In-Reply-To: <20230630033443.2359278-2-mengqinggang@loongson.cn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi, On 6/30/23 11:34, mengqinggang wrote: > [snip] > +static struct loongarch_opcode loongarch_lbt_opcodes[] = > +{ > + /* match, mask, name, format, macro, include, exclude, pinfo. */ > + {0x00000800, 0xfffffc1c, "movgr2scr", "cr0:2,r5:5", 0, 0, 0, 0}, > + {0x00000c00, 0xffffff80, "movscr2gr", "r0:5,cr5:2", 0, 0, 0, 0}, Thanks for amending these two! > [snip] > + {0x00368000, 0xffffc3e0, "setx86j", "r0:5,u10:4", 0, 0, 0, 0}, > + {0x00007800, 0xfffffc00, "setx86loope", "r0:5,r5:5", 0, 0, 0, 0}, > + {0x00007c00, 0xfffffc00, "setx86loopne", "r0:5,r5:5", 0, 0, 0, 0}, But what about these three? "x86set..." could be more consistent, especially given "x86settm" is also around. I didn't notice this in my first review but I've mentioned this part in another reply. > [snip] > + {0x0036c000, 0xffffc3e0, "setarmj", "r0:5,u10:4", 0, 0, 0, 0}, Also here (renaming this to "armsetj" would make the LBT/ARM instruction names entirely consistent).