From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 1E582746C; Thu, 1 Sep 2022 20:02:01 +0000 (UTC) Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 281Jl6l3004365; Thu, 1 Sep 2022 14:47:06 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 281Jl50a004364; Thu, 1 Sep 2022 14:47:05 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Thu, 1 Sep 2022 14:47:05 -0500 From: Segher Boessenkool To: Christophe Leroy Cc: Nathan Chancellor , Michael Ellerman , kernel test robot , Arnd Bergmann , Tom Rix , "llvm@lists.linux.dev" , Nick Desaulniers , "linux-kernel@vger.kernel.org" , Nicholas Piggin , "patches@lists.linux.dev" , "linuxppc-dev@lists.ozlabs.org" Subject: Re: [PATCH] powerpc/math_emu/efp: Include module.h Message-ID: <20220901194705.GI25951@gate.crashing.org> References: <20220831152014.3501664-1-nathan@kernel.org> Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i On Thu, Sep 01, 2022 at 05:41:33AM +0000, Christophe Leroy wrote: > I think it would be worth a GCC bug report. We need a stand-alone testcase for this. When you have created one, at least 98% of the time you discover the bug is in user code after all. Which is a very good thing, it means the problem can be fixed simpler, cheaper, and a lot faster :-) Segher From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9C5B3ECAAD2 for ; Thu, 1 Sep 2022 19:55:06 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4MJWwn10mVz3067 for ; Fri, 2 Sep 2022 05:55:05 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.crashing.org (client-ip=63.228.1.57; helo=gate.crashing.org; envelope-from=segher@kernel.crashing.org; receiver=) Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by lists.ozlabs.org (Postfix) with ESMTP id 4MJWwH2nmdz2xH9 for ; Fri, 2 Sep 2022 05:54:38 +1000 (AEST) Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 281Jl6l3004365; Thu, 1 Sep 2022 14:47:06 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 281Jl50a004364; Thu, 1 Sep 2022 14:47:05 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Thu, 1 Sep 2022 14:47:05 -0500 From: Segher Boessenkool To: Christophe Leroy Subject: Re: [PATCH] powerpc/math_emu/efp: Include module.h Message-ID: <20220901194705.GI25951@gate.crashing.org> References: <20220831152014.3501664-1-nathan@kernel.org> 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-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: kernel test robot , Arnd Bergmann , "llvm@lists.linux.dev" , Nick Desaulniers , "linux-kernel@vger.kernel.org" , Nicholas Piggin , "patches@lists.linux.dev" , Nathan Chancellor , Tom Rix , "linuxppc-dev@lists.ozlabs.org" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Thu, Sep 01, 2022 at 05:41:33AM +0000, Christophe Leroy wrote: > I think it would be worth a GCC bug report. We need a stand-alone testcase for this. When you have created one, at least 98% of the time you discover the bug is in user code after all. Which is a very good thing, it means the problem can be fixed simpler, cheaper, and a lot faster :-) Segher