[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAQhbn-qZg_Bywk8rf0+oZhVbDjJ=PtcKGCL+k4Fp-ijSw@mail.gmail.com>
Date: Fri, 19 Oct 2018 11:41:31 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Leonardo BrĂ¡s <leobras.c@...il.com>,
lkcamp@...ts.libreplanetbr.org,
Matthew Wilcox <willy6545@...il.com>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: Re: [PATCH 1/4] Adds -Wshadow=local on KBUILD_HOSTCFLAGS
On Fri, Oct 19, 2018 at 1:53 AM Borislav Petkov <bp@...en8.de> wrote:
>
> On Fri, Oct 19, 2018 at 01:39:21AM +0900, Masahiro Yamada wrote:
> > It is not realistic to enable this warning option by default.
>
> I believe the question is whether to enable that warning by default in
> KBUILD_HOSTCFLAGS. Enabling it by default for the target kernel is of
> course, too noisy. That's why it is hidden behind W=2 there.
Sorry, I misunderstood the question.
The difference about the noisiness between CC and HOSTCC
is just comes from the amount of source code.
Adding -Wshadow to KBUILD_HOSTCFLAGS emits another warning in Kconfig.
Of course, it is easy to fix.
But, I just started to think this option is a kind of harsh...
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists