Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3537226imw; Mon, 11 Jul 2022 10:27:32 -0700 (PDT) X-Google-Smtp-Source: AGRyM1slYi2lhXGLqMLjJnGYI+8hI8anVf/PmhU7egvpNelpic4uw1oXpcVk5FPBl+tms74o9UsE X-Received: by 2002:a17:906:8a4a:b0:72b:5b23:3065 with SMTP id gx10-20020a1709068a4a00b0072b5b233065mr4765144ejc.557.1657560451892; Mon, 11 Jul 2022 10:27:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657560451; cv=none; d=google.com; s=arc-20160816; b=JepKEu/H7/uHJKpcOnV8YzfOS3gWUE8RSFkuRevD/CUs4FsDUP4wXm78i3CpkTdERX YrYph3oblL05+/I90RYR6pSStzF3A556lf8ynMu2pNa+OckJrwLkdKXRmWSdhoK+ZwrP JZtQ0lPYLT41cxWM8BG3f6ur0ayHdCvliACSMo329VkZ4eSs/Fc4fQQl8dUlHwfK7h5H zBrfI6736/RdYCOLp306MOfk60ofv5Z+y4szmbStsFoTXmwwxm1nxcCMIJvLzIItltrX 26ggrpJgkjSJmBZ2TVoQxUJiUZt7+JsEae6lguonPQvZegeaL01XYWFTAtcG8071qDhS abfA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=IoEI7k3Uf6ZQVEJ+bHigNjcX86a+DaTeLKm4rdZlbig=; b=hC90sH48o21nF4kxB3hTrnC4RYmDBa636DoSL+n3FyHutIaWElUCOMcu7EeOywLRYz LBwZnp1vwvpqJG5c5kvzTh4gJu255gapMi4O20Ut3PJBvBHt7T0JgOl9xBLy+Mg8/H0B hRvl4X0KR9stph3TFGM4EgivGWeyFm7Kad2Wfl1BRFFms+VUe/w5vCRIq0+Hl5cBn9ea U5kAAVLvEDrTEOxVn9qUJBiil57hoeA5M2njImKcr2w92qaxWwy8mAy5i6Ar3tb6JATx 03IKvvC1VxsRu8yz03Y3uk4p1A2o7g+gcL2ReDXkEx2avlr2ml3OJoPyN3mpoLMP0Ifa zIxg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ao8-20020a170907358800b00722e1f93942si9439489ejc.333.2022.07.11.10.27.06; Mon, 11 Jul 2022 10:27:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231274AbiGKRPl (ORCPT + 99 others); Mon, 11 Jul 2022 13:15:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52870 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229477AbiGKRPk (ORCPT ); Mon, 11 Jul 2022 13:15:40 -0400 Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id E58935140F for ; Mon, 11 Jul 2022 10:15:38 -0700 (PDT) Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 26BHCQwP008080; Mon, 11 Jul 2022 12:12:27 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 26BHCQ80008079; Mon, 11 Jul 2022 12:12:26 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Mon, 11 Jul 2022 12:12:26 -0500 From: Segher Boessenkool To: Arnd Bergmann Cc: Christophe Leroy , linuxppc-dev , Linux Kernel Mailing List , Nicholas Piggin Subject: Re: [PATCH v1 4/5] powerpc/44x: Fix build failure with GCC 12 (unrecognized opcode: `wrteei') Message-ID: <20220711171226.GG25951@gate.crashing.org> References: <8abab4888da69ff78b73a56f64d9678a7bf684e9.1657549153.git.christophe.leroy@csgroup.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS,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 lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 11, 2022 at 05:05:04PM +0200, Arnd Bergmann wrote: > Is there any value in building for -mcpu=440 or -mcpu=464 when targeting a 476? The original 440 had a very short pipeline. Later IBM 4xx have a longer pipeline. Getting this right (with -mtune=, or just with -mcpu=) is important for performance. So, no? > Maybe add another !PPC_47x dependency for the first two. Ideally we would also > enforce that 440/464 based boards cannot be selected together with 476, though > I guess that is a separate issue. > > Is there a practical difference between 440 and 464 when building kernels? > gcc seems to treat them the same way, so maybe one option for both is enough > here. -mcpu= is used as the default for -mtune=, so that is always a consideration. PPC464 is treated the same as PPC440 in binutils as well, so I don't think there is any issue there. Segher