From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from xry111.site (xry111.site [89.208.246.23]) by sourceware.org (Postfix) with ESMTPS id B2F0C3858439 for ; Tue, 19 Dec 2023 07:00:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B2F0C3858439 Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=xry111.site Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=xry111.site ARC-Filter: OpenARC Filter v1.0.0 sourceware.org B2F0C3858439 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=89.208.246.23 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702969215; cv=none; b=a99+lY2s0ESbN8coydFbBiIF3HDRTUzmtPcTCSmLy3FFGw/G2KTNnpnc897xTiaPigF7UZTUhuOISJFqlw3KPs78rMNEuoaHAJsJUxZX0lNR3GvKtkXfw/TpEq+OVUM9Ib57S/IG3/5CbuoE/Wf9QhxwvUEyhaHgiq2Y6qkuOJM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702969215; c=relaxed/simple; bh=vxJYjUSkxgENpX0XsYr8pRN3WmOgoq5UH8EKgJjfFkk=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=DXCGfhUi3ss6sUY44fuVGGnoOZTYjR/uo5zoopIRsaaTR/F+DXJey0o+XjCOKga6PlQAQJaObIENuoq3I1sEfYBofmAMnu8EFkVS8NRaU8R7IAKo1mdtoHvTHWGxo2N5xCF9U3m0dlQVQbR6sggMa7ElrA+2WSxCoE9QL0zB95g= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xry111.site; s=default; t=1702969211; bh=vxJYjUSkxgENpX0XsYr8pRN3WmOgoq5UH8EKgJjfFkk=; h=From:To:Cc:Subject:Date:From; b=nnmpflDY5pEtLgyu/bggcEpZ4pwzztteji1XaH1sFr79q+jVD4KNS7S9d8Cb03FzI 8uwTxCsKaRp3eV6qUNE+F08mUU+sVmhMezb42xkre7WlwMgTDLUl15pFBjXLAXITk6 qy9k8NMCQHwQH5QmsKrcQI/4NXv3HjTwbDFbJWhY= Received: from stargazer.. (unknown [IPv6:240e:358:119f:400:dc73:854d:832e:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: xry111@xry111.site) by xry111.site (Postfix) with ESMTPSA id E228066A04; Tue, 19 Dec 2023 02:00:08 -0500 (EST) From: Xi Ruoyao To: gcc-patches@gcc.gnu.org Cc: chenglulu , i@xen0n.name, xuchenghua@loongson.cn, c@jia.je, Xi Ruoyao Subject: [PATCH 0/2] LoongArch: Fix PR113033 and clean up code Date: Tue, 19 Dec 2023 14:59:55 +0800 Message-ID: <20231219065957.70665-1-xry111@xry111.site> X-Mailer: git-send-email 2.43.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,LIKELY_SPAM_FROM,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Superseds https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640871.html. Per Jakub's response, vec_init patterns do not have a predicate on the input operand so the operand can be *anything*. It's not safe to simply move it into an reg, and we have to use force_reg instead. The code clean up is separated into the 2nd patch to make reviewing easier. Bootstrapped and regtested on loongarch64-linux-gnu. Ok for trunk? Xi Ruoyao (2): LoongArch: Use force_reg instead of gen_reg_rtx + emit_move_insn in vec_init expander [PR113033] LoongArch: Clean up vec_init expander gcc/config/loongarch/loongarch.cc | 54 +++++++------------ gcc/testsuite/gcc.target/loongarch/pr113033.c | 23 ++++++++ 2 files changed, 43 insertions(+), 34 deletions(-) create mode 100644 gcc/testsuite/gcc.target/loongarch/pr113033.c -- 2.43.0