From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by sourceware.org (Postfix) with ESMTP id 80AE3398B150 for ; Wed, 9 Jun 2021 14:39:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 80AE3398B150 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=kernel.crashing.org Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 159EcIOc024643; Wed, 9 Jun 2021 09:38:19 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 159EcI8S024642; Wed, 9 Jun 2021 09:38:18 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Wed, 9 Jun 2021 09:38:18 -0500 From: Segher Boessenkool To: Aaron Sawdey Cc: gcc-patches Subject: Re: [PATCH,rs6000] Fix p10 fusion test cases for -m32 Message-ID: <20210609143818.GE18427@gate.crashing.org> References: <1621968336-99949-1-git-send-email-acsawdey@linux.ibm.com> <4320298D-2A9E-4FEC-BD26-25D695CD6AE7@linux.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4320298D-2A9E-4FEC-BD26-25D695CD6AE7@linux.ibm.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-6.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, KAM_NUMSUBJECT, TXREP, T_SPF_HELO_PERMERROR, T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 14:39:21 -0000 On Wed, May 26, 2021 at 04:53:24PM -0500, Aaron Sawdey wrote: > > The counts of fusion insns are slightly different for 32-bit compiles > > so we need different scan-assembler-times counts for 32 and 64 bit > > in the test cases for p10 fusion. Have you checked all of these actually make sense? It seems too be two themes: long long being two regs / two insns on 32-bit, and the you get cmpld etc. only on 64-bit? Okay for trunk if this is actually the expected output. Thanks! Segher