Message ID | 20231206052427.143889-2-guojiufu@linux.ibm.com |
---|---|
State | Unresolved |
Headers |
Return-Path: <gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:bcd1:0:b0:403:3b70:6f57 with SMTP id r17csp3893834vqy; Tue, 5 Dec 2023 21:25:02 -0800 (PST) X-Google-Smtp-Source: AGHT+IERQ78dGIgMPZUUeaiHukcOjD8nFsHXwIr/hj7KPgvhOXQWP7vYJ277TYPoUbEbJ7nZo3Fz X-Received: by 2002:ac8:5c8c:0:b0:423:7255:3c7e with SMTP id r12-20020ac85c8c000000b0042372553c7emr443063qta.17.1701840302295; Tue, 05 Dec 2023 21:25:02 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1701840302; cv=pass; d=google.com; s=arc-20160816; b=rLFCXS901L6z3MsS584xxGY/beMW17KFMUhevWa/bu0SWeJJO6DmIJ5L8QANMMACkw Ncu4OXPo1xN57uvDlyopbIE4lwsq5SQmGuRaGEfHp9P++Ms18OX8kS67fG0RYtsX7vfz dxcsEOE1E47NK364ZS4di4JvmkZyVIBa00L8gzNUnLQnbclGKnXwpGmXWORog1s5JPI0 T5XSYYjRM5GLx/F178IzWMnizV8tl0xHivF1tyHJh0ZetlAHBGRilmIom/HVkkv8y+JZ zXxQTMrF7nHKzQJmd2x+NBEQkLwuorYrIedUuOIFrPK4NM8HaZFOFQFf4R0d/c+JvRtY cwig== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=errors-to:list-subscribe:list-help:list-post:list-archive :list-unsubscribe:list-id:precedence:mime-version :content-transfer-encoding:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-filter:dmarc-filter :delivered-to; bh=NNO2GGo7IN/7DS6zea0LEOdzmAJrhjWkkiPp8xjQhoY=; fh=AJ+XyiCK9C45D31PcueuCqgpHIDRP2j25uBOQsJKm1w=; b=Xaasq20zrni1qlM6sEXNrqcE9NdG8UzPutg+V2pG0jniaEHtxQrK1/Fa9jFyx6g2gY jtV1eYWy6tqxab2eU3Oz0vsdcOpZCgSUdFJt5lJ45p9ywk3RGuyEcpzxLfdqG0dOJxbR 5wacJO1RmDoAIONaicROO5J43en24CUbvfgwzoPL3JluvbFYLpaAtSvG9xAuO/KQ8xtR l712UgVD24VMPlgg5n/XImsR1c28Mx7hMPyZy4FFjyr5fUxt0SMfb8Q8PLYvPHG/lFVc rVK2ausbHI1TQA1A3N6vF/BAcSFMgXzQFXkP4F+IHDlrPt8aydfg4waf/yhLbapuKDEx dUsA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=r7dHFsoU; arc=pass (i=1); spf=pass (google.com: domain of gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org designates 8.43.85.97 as permitted sender) smtp.mailfrom="gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org"; dmarc=pass (p=REJECT sp=NONE dis=NONE) header.from=ibm.com Received: from server2.sourceware.org (server2.sourceware.org. [8.43.85.97]) by mx.google.com with ESMTPS id i16-20020ac860d0000000b004236ea250e1si12464512qtm.514.2023.12.05.21.25.02 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Dec 2023 21:25:02 -0800 (PST) Received-SPF: pass (google.com: domain of gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org designates 8.43.85.97 as permitted sender) client-ip=8.43.85.97; Authentication-Results: mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=r7dHFsoU; arc=pass (i=1); spf=pass (google.com: domain of gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org designates 8.43.85.97 as permitted sender) smtp.mailfrom="gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org"; dmarc=pass (p=REJECT sp=NONE dis=NONE) header.from=ibm.com Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 17082385F028 for <ouuuleilei@gmail.com>; Wed, 6 Dec 2023 05:25:02 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by sourceware.org (Postfix) with ESMTPS id C01343857C51; Wed, 6 Dec 2023 05:24:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C01343857C51 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linux.ibm.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C01343857C51 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=148.163.156.1 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701840279; cv=none; b=e9xbbRnLW3yffdrFOFMHTR0/I0TM3/5uLR7pexBH7FpttbD2BMTXYkRQlK6wMr3SQdmetR6I5QqpJ5fWHon1sFScjVqLkwEQ5v0a7s2/r8iZFaz72A3Z6DU9d4dqLYMCjFgnRFBWbmtw882WMuqI6XwhRrKm83xmF8eWi/4MI8s= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701840279; c=relaxed/simple; bh=RMBZiIU6oAXXefqViQdUpb/gtfR7Q8hJS6DDVvDzDcM=; h=DKIM-Signature:From:To:Subject:Date:Message-Id:MIME-Version; b=WBFLmplQ5wOV79SLNKFnInLWNlQOumbwmFjYR65lCtiic7FpjDWewYGs7uyEOvfxAsUJ/d2Q+DjmlZ7Dwvbbfn9MGQB4notwI14//y9fOUT6caZDcuu9e88Z2j7x7YoBli1asNO4aKqziQDfWeSf8WIXynSR1EFGTgYTA/Xb3/0= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from pps.filterd (m0353729.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3B65MVXH010502; Wed, 6 Dec 2023 05:24:35 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : content-transfer-encoding : mime-version; s=pp1; bh=NNO2GGo7IN/7DS6zea0LEOdzmAJrhjWkkiPp8xjQhoY=; b=r7dHFsoURJYq1zMYYlYe6pL317zbSXW9LMYOfgPUynEg+Cp3/X4Fw8hxLthMeaNlg5U3 46vVKFuUIbVvlFVjNL4llknoSW1RmKitXZOy5BvnF9LLjLG66dDlYH4xAOfiAU2XfaWd Qgm98hm6gjPNQ1NeneszfzGyfj3WSUqe8TzSRGRwecn0RJZkXtCke6OwGY0OYWZA6w7s z5JK1NKX3kIW+UhTxxH7A6MUZuY4VNMDnnefagtx5m/yHWMQPqMiN7yXtAjFPEPElUCr /ZYrvrn9qoOTIHxY4dRIZCG5dfpPYwku6werL6XKGkEDV+j5qgmlK5KNbzzKrAfb4s5j iA== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3utjrd81cf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 06 Dec 2023 05:24:35 +0000 Received: from m0353729.ppops.net (m0353729.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 3B65NIso013742; Wed, 6 Dec 2023 05:24:34 GMT Received: from ppma12.dal12v.mail.ibm.com (dc.9e.1632.ip4.static.sl-reverse.com [50.22.158.220]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3utjrd81c0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 06 Dec 2023 05:24:34 +0000 Received: from pps.filterd (ppma12.dal12v.mail.ibm.com [127.0.0.1]) by ppma12.dal12v.mail.ibm.com (8.17.1.19/8.17.1.19) with ESMTP id 3B65KHM4020810; Wed, 6 Dec 2023 05:24:33 GMT Received: from smtprelay02.fra02v.mail.ibm.com ([9.218.2.226]) by ppma12.dal12v.mail.ibm.com (PPS) with ESMTPS id 3utav4ab0m-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 06 Dec 2023 05:24:33 +0000 Received: from smtpav04.fra02v.mail.ibm.com (smtpav04.fra02v.mail.ibm.com [10.20.54.103]) by smtprelay02.fra02v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 3B65OUOK27263564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 6 Dec 2023 05:24:30 GMT Received: from smtpav04.fra02v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9A77B2004E; Wed, 6 Dec 2023 05:24:30 +0000 (GMT) Received: from smtpav04.fra02v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8143B20040; Wed, 6 Dec 2023 05:24:29 +0000 (GMT) Received: from genoa.aus.stglabs.ibm.com (unknown [9.40.192.157]) by smtpav04.fra02v.mail.ibm.com (Postfix) with ESMTP; Wed, 6 Dec 2023 05:24:29 +0000 (GMT) From: Jiufu Guo <guojiufu@linux.ibm.com> To: gcc-patches@gcc.gnu.org Cc: segher@kernel.crashing.org, dje.gcc@gmail.com, linkw@gcc.gnu.org, bergner@linux.ibm.com, guojiufu@linux.ibm.com Subject: [PATCH V3 2/3] Using pli for constant splitting Date: Wed, 6 Dec 2023 13:24:26 +0800 Message-Id: <20231206052427.143889-2-guojiufu@linux.ibm.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20231206052427.143889-1-guojiufu@linux.ibm.com> References: <20231206052427.143889-1-guojiufu@linux.ibm.com> X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: cZRfQdMxqK0aR2cP73Uc968b27VgPvu_ X-Proofpoint-GUID: AMV0hdaF3ztmLjebUDTzWqzotISt0RiE Content-Transfer-Encoding: 8bit X-Proofpoint-UnRewURL: 0 URL was un-rewritten MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.997,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-12-06_04,2023-12-05_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 adultscore=0 priorityscore=1501 lowpriorityscore=0 mlxlogscore=999 suspectscore=0 spamscore=0 malwarescore=0 clxscore=1011 mlxscore=0 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2311290000 definitions=main-2312060043 X-Spam-Status: No, score=-10.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_EF, GIT_PATCH_0, KAM_SHORT, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, 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 X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org> List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe> List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/> List-Post: <mailto:gcc-patches@gcc.gnu.org> List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help> List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe> Errors-To: gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1784508897017776441 X-GMAIL-MSGID: 1784508897017776441 |
Series |
[V3,1/3] rs6000: update num_insns_constant for 2 insns
|
|
Checks
Context | Check | Description |
---|---|---|
snail/gcc-patch-check | warning | Git am fail log |
Commit Message
Jiufu Guo
Dec. 6, 2023, 5:24 a.m. UTC
Hi, For constant building e.g. r120=0x66666666, which does not fit 'li or lis', 'pli' is used to build this constant via 'emit_move_insn'. While for a complicated constant, e.g. 0x6666666666666666ULL, when using 'rs6000_emit_set_long_const' to split the constant recursively, it fails to use 'pli' to build the half part constant: 0x66666666. 'rs6000_emit_set_long_const' could be updated to use 'pli' to build half part of the constant when necessary. For example: 0x6666666666666666ULL, "pli 3,1717986918; rldimi 3,3,32,0" can be used. Compare with previous: https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636567.html This verion is refreshed and added with a new testcase. Bootstrap®test pass on ppc64{,le}. Is this ok for trunk? BR, Jeff (Jiufu Guo) gcc/ChangeLog: * config/rs6000/rs6000.cc (rs6000_emit_set_long_const): Add code to use pli for 34bit constant. gcc/testsuite/ChangeLog: * gcc.target/powerpc/const_split_pli.c: New test. --- gcc/config/rs6000/rs6000.cc | 7 +++++++ gcc/testsuite/gcc.target/powerpc/const_split_pli.c | 9 +++++++++ 2 files changed, 16 insertions(+) create mode 100644 gcc/testsuite/gcc.target/powerpc/const_split_pli.c
Comments
Hi Jeff, on 2023/12/6 13:24, Jiufu Guo wrote: > Hi, > > For constant building e.g. r120=0x66666666, which does not fit 'li or lis', > 'pli' is used to build this constant via 'emit_move_insn'. > > While for a complicated constant, e.g. 0x6666666666666666ULL, when using > 'rs6000_emit_set_long_const' to split the constant recursively, it fails to > use 'pli' to build the half part constant: 0x66666666. > > 'rs6000_emit_set_long_const' could be updated to use 'pli' to build half > part of the constant when necessary. For example: 0x6666666666666666ULL, > "pli 3,1717986918; rldimi 3,3,32,0" can be used. > > Compare with previous: > https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636567.html > This verion is refreshed and added with a new testcase. > > Bootstrap®test pass on ppc64{,le}. > Is this ok for trunk? > > BR, > Jeff (Jiufu Guo) > > gcc/ChangeLog: > > * config/rs6000/rs6000.cc (rs6000_emit_set_long_const): Add code to use > pli for 34bit constant. > > gcc/testsuite/ChangeLog: > > * gcc.target/powerpc/const_split_pli.c: New test. Nit: Now we have: gcc/testsuite/gcc.target/powerpc/const-build.c gcc/testsuite/gcc.target/powerpc/const_anchors.c gcc/testsuite/gcc.target/powerpc/const-compare.c I prefer the name of this new case is like const-build-1.c (put a detailed comment inside) or const-build-split-pli.c, to align with the existing. > > --- > gcc/config/rs6000/rs6000.cc | 7 +++++++ > gcc/testsuite/gcc.target/powerpc/const_split_pli.c | 9 +++++++++ > 2 files changed, 16 insertions(+) > create mode 100644 gcc/testsuite/gcc.target/powerpc/const_split_pli.c > > diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc > index dbdc72dce5d..2e074a21a05 100644 > --- a/gcc/config/rs6000/rs6000.cc > +++ b/gcc/config/rs6000/rs6000.cc > @@ -10509,6 +10509,13 @@ rs6000_emit_set_long_const (rtx dest, HOST_WIDE_INT c, int *num_insns) > GEN_INT (0xffffffff))); > }; > > + if (TARGET_PREFIXED && SIGNED_INTEGER_34BIT_P (c)) > + { > + /* li/lis/pli */ > + count_or_emit_insn (dest, GEN_INT (c)); > + return; > + } > + > if ((ud4 == 0xffff && ud3 == 0xffff && ud2 == 0xffff && (ud1 & 0x8000)) > || (ud4 == 0 && ud3 == 0 && ud2 == 0 && !(ud1 & 0x8000))) > { > diff --git a/gcc/testsuite/gcc.target/powerpc/const_split_pli.c b/gcc/testsuite/gcc.target/powerpc/const_split_pli.c > new file mode 100644 > index 00000000000..626c93084aa > --- /dev/null > +++ b/gcc/testsuite/gcc.target/powerpc/const_split_pli.c > @@ -0,0 +1,9 @@ > +/* { dg-do compile { target lp64 } } */ > +/* { dg-options "-O2" } */ It needs -mdejagnu-cpu=power10 as well. > +/* { dg-require-effective-target power10_ok } */ > + > +unsigned long long msk66() { return 0x6666666666666666ULL; } > + > +/* { dg-final { scan-assembler-times {\mpli\M} 1 } } */ > +/* { dg-final { scan-assembler-not {\mli\M} } } */ > +/* { dg-final { scan-assembler-not {\mlis\M} } } */ OK for trunk with the above nits tweaked, thanks! BR, Kewen
Hi, Thanks for your insight and helpful review! "Kewen.Lin" <linkw@linux.ibm.com> writes: > Hi Jeff, > > on 2023/12/6 13:24, Jiufu Guo wrote: >> Hi, >> >> For constant building e.g. r120=0x66666666, which does not fit 'li or lis', >> 'pli' is used to build this constant via 'emit_move_insn'. >> >> While for a complicated constant, e.g. 0x6666666666666666ULL, when using >> 'rs6000_emit_set_long_const' to split the constant recursively, it fails to >> use 'pli' to build the half part constant: 0x66666666. >> >> 'rs6000_emit_set_long_const' could be updated to use 'pli' to build half >> part of the constant when necessary. For example: 0x6666666666666666ULL, >> "pli 3,1717986918; rldimi 3,3,32,0" can be used. >> >> Compare with previous: >> https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636567.html >> This verion is refreshed and added with a new testcase. >> >> Bootstrap®test pass on ppc64{,le}. >> Is this ok for trunk? >> >> BR, >> Jeff (Jiufu Guo) >> >> gcc/ChangeLog: >> >> * config/rs6000/rs6000.cc (rs6000_emit_set_long_const): Add code to use >> pli for 34bit constant. >> >> gcc/testsuite/ChangeLog: >> >> * gcc.target/powerpc/const_split_pli.c: New test. > > Nit: Now we have: > > gcc/testsuite/gcc.target/powerpc/const-build.c > gcc/testsuite/gcc.target/powerpc/const_anchors.c > gcc/testsuite/gcc.target/powerpc/const-compare.c > > I prefer the name of this new case is like const-build-1.c > (put a detailed comment inside) or const-build-split-pli.c, > to align with the existing. Thanks! > >> >> --- >> gcc/config/rs6000/rs6000.cc | 7 +++++++ >> gcc/testsuite/gcc.target/powerpc/const_split_pli.c | 9 +++++++++ >> 2 files changed, 16 insertions(+) >> create mode 100644 gcc/testsuite/gcc.target/powerpc/const_split_pli.c >> >> diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc >> index dbdc72dce5d..2e074a21a05 100644 >> --- a/gcc/config/rs6000/rs6000.cc >> +++ b/gcc/config/rs6000/rs6000.cc >> @@ -10509,6 +10509,13 @@ rs6000_emit_set_long_const (rtx dest, HOST_WIDE_INT c, int *num_insns) >> GEN_INT (0xffffffff))); >> }; >> >> + if (TARGET_PREFIXED && SIGNED_INTEGER_34BIT_P (c)) >> + { >> + /* li/lis/pli */ >> + count_or_emit_insn (dest, GEN_INT (c)); >> + return; >> + } >> + >> if ((ud4 == 0xffff && ud3 == 0xffff && ud2 == 0xffff && (ud1 & 0x8000)) >> || (ud4 == 0 && ud3 == 0 && ud2 == 0 && !(ud1 & 0x8000))) >> { >> diff --git a/gcc/testsuite/gcc.target/powerpc/const_split_pli.c b/gcc/testsuite/gcc.target/powerpc/const_split_pli.c >> new file mode 100644 >> index 00000000000..626c93084aa >> --- /dev/null >> +++ b/gcc/testsuite/gcc.target/powerpc/const_split_pli.c >> @@ -0,0 +1,9 @@ >> +/* { dg-do compile { target lp64 } } */ >> +/* { dg-options "-O2" } */ > > It needs -mdejagnu-cpu=power10 as well. Yeap, thanks. > >> +/* { dg-require-effective-target power10_ok } */ >> + >> +unsigned long long msk66() { return 0x6666666666666666ULL; } >> + >> +/* { dg-final { scan-assembler-times {\mpli\M} 1 } } */ >> +/* { dg-final { scan-assembler-not {\mli\M} } } */ >> +/* { dg-final { scan-assembler-not {\mlis\M} } } */ > > OK for trunk with the above nits tweaked, thanks! > > BR, > Kewen
diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc index dbdc72dce5d..2e074a21a05 100644 --- a/gcc/config/rs6000/rs6000.cc +++ b/gcc/config/rs6000/rs6000.cc @@ -10509,6 +10509,13 @@ rs6000_emit_set_long_const (rtx dest, HOST_WIDE_INT c, int *num_insns) GEN_INT (0xffffffff))); }; + if (TARGET_PREFIXED && SIGNED_INTEGER_34BIT_P (c)) + { + /* li/lis/pli */ + count_or_emit_insn (dest, GEN_INT (c)); + return; + } + if ((ud4 == 0xffff && ud3 == 0xffff && ud2 == 0xffff && (ud1 & 0x8000)) || (ud4 == 0 && ud3 == 0 && ud2 == 0 && !(ud1 & 0x8000))) { diff --git a/gcc/testsuite/gcc.target/powerpc/const_split_pli.c b/gcc/testsuite/gcc.target/powerpc/const_split_pli.c new file mode 100644 index 00000000000..626c93084aa --- /dev/null +++ b/gcc/testsuite/gcc.target/powerpc/const_split_pli.c @@ -0,0 +1,9 @@ +/* { dg-do compile { target lp64 } } */ +/* { dg-options "-O2" } */ +/* { dg-require-effective-target power10_ok } */ + +unsigned long long msk66() { return 0x6666666666666666ULL; } + +/* { dg-final { scan-assembler-times {\mpli\M} 1 } } */ +/* { dg-final { scan-assembler-not {\mli\M} } } */ +/* { dg-final { scan-assembler-not {\mlis\M} } } */