From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) by sourceware.org (Postfix) with ESMTPS id 420093858010 for ; Wed, 4 May 2022 10:07:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 420093858010 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=codesourcery.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=m.gmane-mx.org Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nmBun-0002Y1-Iy for gcc@gcc.gnu.org; Wed, 04 May 2022 12:07:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gcc@gcc.gnu.org From: Julian Brown Subject: Re: Multiple types of load/store: how to create .md rules? Date: Wed, 4 May 2022 11:07:10 +0100 Organization: Siemens Message-ID: <20220504110710.3c4936cc@squid.athome> References: <0f574adfe4c15da62238eeba1c939414a4a23198.camel@tantosonline.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In-Reply-To: <0f574adfe4c15da62238eeba1c939414a4a23198.camel@tantosonline.com> X-Newsreader: Claws Mail 4.0.0 (GTK+ 3.24.31; x86_64-pc-linux-gnu) X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, KAM_SHORT, MEDICAL_SUBJECT, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2022 10:07:28 -0000 On Mon, 02 May 2022 19:10:41 -0700 Andras Tantos wrote: > To a previous problem I've asked, Andrew Pinski replied that I should > merge all *movsi patterns into a single one to avoid (in that case) > strange deletions in the generated assembly. Is that possible here? It > appears to me that I would need the ability to differentiate the > different patterns using constraints, but is there a way to define > custom versions of the 'm' pattern? I didn't find anything on that in > the documentation. Did I miss something? Check "define_memory_constraint" in existing ports, i.e.: https://gcc.gnu.org/onlinedocs/gccint/Define-Constraints.html#index-define_005fmemory_005fconstraint HTH, Julian