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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 90C2BECAAD2 for ; Thu, 1 Sep 2022 19:55:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231650AbiIATzu (ORCPT ); Thu, 1 Sep 2022 15:55:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43998 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233249AbiIATzq (ORCPT ); Thu, 1 Sep 2022 15:55:46 -0400 Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 0E570564F5 for ; Thu, 1 Sep 2022 12:55:43 -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 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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