From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104642 invoked by alias); 20 May 2019 19:47:51 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 104633 invoked by uid 89); 20 May 2019 19:47:50 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_00,MEDICAL_SUBJECT,SPF_HELO_PASS autolearn=no version=3.3.1 spammy=opinions X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 20 May 2019 19:47:49 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 4807B356E4; Mon, 20 May 2019 19:47:40 +0000 (UTC) Received: from localhost.localdomain (ovpn-112-8.rdu2.redhat.com [10.10.112.8]) by smtp.corp.redhat.com (Postfix) with ESMTP id 899C05D704; Mon, 20 May 2019 19:47:38 +0000 (UTC) Subject: Re: New .md construct: define_insn_and_rewrite To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com References: From: Jeff Law Openpgp: preference=signencrypt Message-ID: Date: Mon, 20 May 2019 19:47:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg01310.txt.bz2 On 5/14/19 8:14 AM, Richard Sandiford wrote: > Several SVE patterns need define_insn_and_splits that generate the > same insn_code, but with different operands. That's probably a > niche requirement, but it's cropping up often enough on the ACLE > branch that I think it would be good to have a syntactic sugar for it. > > This patch therefore adds a new construct called define_insn_and_rewrite. > It's basically a define_insn_and_split with an implicit split pattern, > obtained by copying the insn pattern and replacing match_operands with > match_dups and match_operators with match_op_dups. > > Any comments? Suggestions for better names? No strong opinions here other than to mention that I think there's other places we could use this. Jeff