From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: kernel test robot <lkp@intel.com>, Arnd Bergmann <arnd@arndb.de>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
Nick Desaulniers <ndesaulniers@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
Nathan Chancellor <nathan@kernel.org>, Tom Rix <trix@redhat.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/math_emu/efp: Include module.h
Date: Fri, 2 Sep 2022 08:43:49 +0000 [thread overview]
Message-ID: <ae2ee2d8-ec0a-d0ab-2c5a-b9a8c7579093@csgroup.eu> (raw)
In-Reply-To: <20220901194705.GI25951@gate.crashing.org>
Le 01/09/2022 à 21:47, Segher Boessenkool a écrit :
> 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 :-)
Easy to reproduce with a .c file that has a single line:
non_existing_macro(xxx);
Apparently that's due to the -w option in arch/powerpc/math_emu/Makefile:
ccflags-y = -w
Was introduced by commit d2b194ed8208 ("powerpc/math-emu: Use kernel
generic math-emu code")
If I understand correctly it means 'ignore all warnings'. Then it seems
CLANG doesn't honor that request.
Christophe
next prev parent reply other threads:[~2022-09-02 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 15:20 [PATCH] powerpc/math_emu/efp: Include module.h Nathan Chancellor
2022-09-01 5:41 ` Christophe Leroy
2022-09-01 19:47 ` Segher Boessenkool
2022-09-02 8:43 ` Christophe Leroy [this message]
2022-09-02 12:40 ` Segher Boessenkool
2022-09-09 12:06 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae2ee2d8-ec0a-d0ab-2c5a-b9a8c7579093@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
--cc=patches@lists.linux.dev \
--cc=segher@kernel.crashing.org \
--cc=trix@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).