From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by sourceware.org (Postfix) with ESMTPS id D49DC385AC2C for ; Fri, 8 Dec 2023 08:01:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D49DC385AC2C 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 D49DC385AC2C 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=1702022524; cv=none; b=L7J4DsJEBm6iuVsmhwfSnXIDt3bJeWbJwDxC4lAxicJicMMDz2+xopP3eyThaNPI9XjzS6PbzE04++Of5B5s/fydR8QV/potl6TCOPbg63DYUTtWxIvpAIl6s7lwim0Qdr8TfPahXcZzsQQqQsjEwmFAnFs7Ynbxfjr1N3uYjnQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702022524; c=relaxed/simple; bh=jPrgKx/bln8ASsustfjOowLbMJjqQ8jF0Gic0Osmgcw=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:From:To; b=XoJP4LFBk1y4csoGCPu60mgztXv1hPq+1x083I+s5kvyPMWdFZ0qlw/pUBIh85WCiJQ3hrhk5wjMv1PfVBqUI0TEQkg//Sn1IZlAhPtYC3ZJ1SP+wzMmv7CNqzlU+VhxTb/xOCZ4BIwxbsubkhPcergqqi3cX6mLtSFUAoaf0CQ= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from pps.filterd (m0360083.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3B87l2ud031466; Fri, 8 Dec 2023 08:01:56 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=message-id : date : mime-version : subject : from : to : cc : references : in-reply-to : content-type : content-transfer-encoding; s=pp1; bh=S41+Q7TcwD0dRh7S5YaW6Es83v8h6VRGaZY4DQPyN5M=; b=rTWbmbZdpP6A6TD3qbDeMhEQBaComJ9/OA5NkYi0Ihmb6scVmNA3JsaZhO/7c6tXTFXm klTJoezOBgjD0wzDXzaiEMYyfW4/kdFca0nZUitz6Q/YOAMlvu1NzWvm8SVj+bAZLea8 f2ztBTWjdutHQ6KrDuynAw1eVyxQsDCtmFvf/2mWBVxQw6+54F0dY8GVZfQ1VGscZ4Nt 0CfM4gE+Au4JWWZ0kz/KPz2KYvyvIdhjgJ/UdIQDAgiGhEGksnYh+zKBUobL6I9FtJRP 1yeni1UOIqOI9vPNjqrhWzfPbfIJyF47GxNdJPzrPFXhiSd1ka64xfRAo2tl1cS9DJNf PA== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3uuy2a0g00-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 08 Dec 2023 08:01:56 +0000 Received: from m0360083.ppops.net (m0360083.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 3B87lFrH032009; Fri, 8 Dec 2023 08:01:56 GMT Received: from ppma23.wdc07v.mail.ibm.com (5d.69.3da9.ip4.static.sl-reverse.com [169.61.105.93]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3uuy2a0fyb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 08 Dec 2023 08:01:55 +0000 Received: from pps.filterd (ppma23.wdc07v.mail.ibm.com [127.0.0.1]) by ppma23.wdc07v.mail.ibm.com (8.17.1.19/8.17.1.19) with ESMTP id 3B86C6FA013762; Fri, 8 Dec 2023 08:01:54 GMT Received: from smtprelay04.wdc07v.mail.ibm.com ([172.16.1.71]) by ppma23.wdc07v.mail.ibm.com (PPS) with ESMTPS id 3utau4gcpr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 08 Dec 2023 08:01:54 +0000 Received: from smtpav01.wdc07v.mail.ibm.com (smtpav01.wdc07v.mail.ibm.com [10.39.53.228]) by smtprelay04.wdc07v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 3B881rb440632836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 8 Dec 2023 08:01:53 GMT Received: from smtpav01.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 69E4758059; Fri, 8 Dec 2023 08:01:53 +0000 (GMT) Received: from smtpav01.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9710C5804B; Fri, 8 Dec 2023 08:01:50 +0000 (GMT) Received: from [9.43.2.117] (unknown [9.43.2.117]) by smtpav01.wdc07v.mail.ibm.com (Postfix) with ESMTP; Fri, 8 Dec 2023 08:01:50 +0000 (GMT) Message-ID: <75bdc1fc-23c9-4ca2-a338-fc1328319114@linux.ibm.com> Date: Fri, 8 Dec 2023 13:31:48 +0530 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2] rs6000: Add new pass for replacement of contiguous addresses vector load lxv with lxvp Content-Language: en-US From: Ajit Agarwal To: "Kewen.Lin" Cc: Segher Boessenkool , David Edelsohn , Peter Bergner , Michael Meissner , GCC Patches References: <77426697-1571-e180-add9-cfb6d10f8424@linux.ibm.com> <57d3fbcb-98b6-4658-8d08-e30f8c68a18c@linux.ibm.com> <11198028-5b04-4ebd-9374-a78dc85376a8@linux.ibm.com> <5467f44c-7b16-444d-a292-8da237f7a9f5@linux.ibm.com> In-Reply-To: <5467f44c-7b16-444d-a292-8da237f7a9f5@linux.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 X-Proofpoint-GUID: W7Ukn9ziVJzFfxkz9csGQusdxdsGzGa8 X-Proofpoint-ORIG-GUID: 0Z0fDxArnxVSlJMu5dbWvOeaHJ-eBqXJ 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-08_04,2023-12-07_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 lowpriorityscore=0 adultscore=0 phishscore=0 priorityscore=1501 spamscore=0 suspectscore=0 bulkscore=0 impostorscore=0 mlxscore=0 mlxlogscore=999 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2311290000 definitions=main-2312080065 X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,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 List-Id: Hello Kewen: On 07/12/23 4:31 pm, Ajit Agarwal wrote: > Hello Kewen: > > On 06/12/23 7:52 am, Kewen.Lin wrote: >> on 2023/12/6 02:01, Ajit Agarwal wrote: >>> Hello Kewen: >>> >>> >>> On 05/12/23 7:13 pm, Ajit Agarwal wrote: >>>> Hello Kewen: >>>> >>>> On 04/12/23 7:31 am, Kewen.Lin wrote: >>>>> Hi Ajit, >>>>> >>>>> on 2023/12/1 17:10, Ajit Agarwal wrote: >>>>>> Hello Kewen: >>>>>> >>>>>> On 24/11/23 3:01 pm, Kewen.Lin wrote: >>>>>>> Hi Ajit, >>>>>>> >>>>>>> Don't forget to CC David (CC-ed) :), some comments are inlined below. >>>>>>> >>>>>>> on 2023/10/8 03:04, Ajit Agarwal wrote: >>>>>>>> Hello All: >>>>>>>> >>>>>>>> This patch add new pass to replace contiguous addresses vector load lxv with mma instruction >>>>>>>> lxvp. >>>>>>> >>>>>>> IMHO the current binding lxvp (and lxvpx, stxvp{x,}) to MMA looks wrong, it's only >>>>>>> Power10 and VSX required, these instructions should perform well without MMA support. >>>>>>> So one patch to separate their support from MMA seems to go first. >>>>>>> >>>>>> >>>>>> I will make the changes for Power10 and VSX. >>>>>> >>>>>>>> This patch addresses one regressions failure in ARM architecture. >>>>>>> >>>>>>> Could you explain this? I don't see any test case for this. >>>>>> >>>>>> I have submitted v1 of the patch and there were regressions failure for Linaro. >>>>>> I have fixed in version V2. >>>>> >>>>> OK, thanks for clarifying. So some unexpected changes on generic code in v1 >>>>> caused the failure exposed on arm. >>>>> >>>>>> >>>>>> >>>>>>> Besides, it seems a bad idea to put this pass after reload? as register allocation >>>>>>> finishes, this pairing has to be restricted by the reg No. (I didn't see any >>>>>>> checking on the reg No. relationship for paring btw.) >>>>>>> >>>>>> >>>>>> Adding before reload pass deletes one of the lxv and replaced with lxvp. This >>>>>> fails in reload pass while freeing reg_eqivs as ira populates them and then >>>>> >>>>> I can't find reg_eqivs, I guessed you meant reg_equivs and moved this pass right before >>>>> pass_reload (between pass_ira and pass_reload)? IMHO it's unexpected as those two passes >>>>> are closely correlated. I was expecting to put it somewhere before ira. >>>> >>>> Yes they are tied together and moving before reload will not work. >>>> >>>>> >>>>>> vecload pass deletes some of insns and while freeing in reload pass as insn >>>>>> is already deleted in vecload pass reload pass segfaults. >>>>>> >>>>>> Moving vecload pass before ira will not make register pairs with lxvp and >>>>>> in ira and that will be a problem. >>>>> >>>>> Could you elaborate the obstacle for moving such pass before pass_ira? >>>>> >>>>> Basing on the status quo, the lxvp is bundled with OOmode, then I'd expect >>>>> we can generate OOmode move (load) and use the components with unspec (or >>>>> subreg with Peter's patch) to replace all the previous use places, it looks >>>>> doable to me. >>>> >>>> Moving before ira passes, we delete the offset lxv and generate lxvp and replace all >>>> the uses, that I am doing. But the offset lxvp register generated by ira are not >>>> register pair and generate random register and hence we cannot generate lxvp. >>>> >>>> For example one lxv is generated with register 32 and other pair is generated >>>> with register 45 by ira if we move it before ira passes. >>> >>> It generates the following. >>> lxvp %vs32,0(%r4) >>> xvf32ger 0,%vs34,%vs32 >>> xvf32gerpp 0,%vs34,%vs45 >> >> What do the RTL insns for these insns look like? >> >> I'd expect you use UNSPEC_MMA_EXTRACT to extract V16QI from the result of lxvp, >> the current define_insn_and_split "*vsx_disassemble_pair" should be able to take >> care of it further (eg: reg and regoff). >> > > Yes with UNSPEC_MMA_EXTRACT it generates lxvp with register pair instead of random > register by ira and reload pass. But there is an extra moves that gets generated. > With UNSPEC_MMA_EXTRACT I could generate the register pair but functionally here is the below code which is incorrect. l lxvp %vs0,0(%r4) xxlor %vs32,%vs0,%vs0 xvf32ger 0,%vs34,%vs32 xvf32gerpp 0,%vs34,%vs33 xxmfacc 0 stxvp %vs2,0(%r3) stxvp %vs0,32(%r3) blr Here is the RTL Code: (insn 19 4 20 2 (set (reg:OO 124 [ *ptr_4(D) ]) (mem:OO (reg/v/f:DI 122 [ ptr ]) [0 *ptr_4(D)+0 S16 A128])) -1 (nil)) (insn 20 19 9 2 (set (reg:V16QI 129 [orig:124 *ptr_4(D) ] [124]) (subreg:V16QI (reg:OO 124 [ *ptr_4(D) ]) 0)) -1 (nil)) (insn 9 20 11 2 (set (reg:XO 119 [ _7 ]) (unspec:XO [ (reg/v:V16QI 123 [ src ]) (reg:V16QI 129 [orig:124 *ptr_4(D) ] [124]) ] UNSPEC_MMA_XVF32GER)) 2195 {mma_xvf32ger} (expr_list:REG_DEAD (reg:OO 124 [ *ptr_4(D) ]) (nil))) (insn 11 9 12 2 (set (reg:XO 120 [ _9 ]) (unspec:XO [ (reg:XO 119 [ _7 ]) (reg/v:V16QI 123 [ src ]) (reg:V16QI 125 [ MEM[(__vector unsigned char *)ptr_4(D) + 16B] ]) ] UNSPEC_MMA_XVF32GERPP)) 2209 {mma_xvf32gerpp} (expr_list:REG_DEAD (reg:V16QI 125 [ MEM[(__vector unsigned char *)ptr_4(D) + 16B] ]) (expr_list:REG_DEAD (reg/v:V16QI 123 [ src ]) (expr_list:REG_DEAD (reg:XO 119 [ _7 ]) (nil))))) (insn 12 11 18 2 (set (mem:XO (reg:DI 126) [1 *dst_10(D)+0 S64 A128]) (reg:XO 120 [ _9 ])) "../gcc/testsuite/g++.target/powerpc/vecload.C":13:8 2182 {*movxo} (expr_list:REG_DEAD (reg:DI 126) (expr_list:REG_DEAD (reg:XO 120 [ _9 ]) (nil)))) (note 18 12 0 NOTE_INSN_DELETED) r124 and r129 conflicts live range amd ira generates different registers which will not serve our purpose. Making r124 and r129 as same will not allocate register by ira as r124 could have both OOmode and V16QImode. Doing this pass before ira_pass has such above issues and we could solve them after making after reload pass. Please suggest. Thanks & Regards Ajit > I am working further on this and send the new version of the patch with all the > comments incorporated. > > Thanks & Regards > Ajit >> BR, >> Kewen >> >>> xxmfacc 0 >>> stxvp %vs2,0(%r3) >>> stxvp %vs0,32(%r3) >>> blr >>> >>> >>> Instead of vs33 ira generates vs45 if we move before pass_ira. >>> >>> Thanks & Regards >>> Ajit >>> >>> >>>> Thanks & Regards >>>> Ajit >>>>> >>>> >>>>>> >>>>>> Making after reload pass is the only solution I see as ira and reload pass >>>>>> makes register pairs and vecload pass will be easier with generation of >>>>>> lxvp. >>>>>> >>>>>> Please suggest. >>>>>> >>>>>>> Looking forward to the comments from Segher/David/Peter/Mike etc. >>>>> >>>>> Still looking forward. :) >>>>> >>>>> BR, >>>>> Kewen >>