linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Stephen Boyd <swboyd@chromium.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Peter Smith <peter.smith@linaro.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH v3] kbuild: Check for unknown options with cc-option usage in Kconfig and clang
Date: Wed, 31 Jul 2019 01:51:50 +0900	[thread overview]
Message-ID: <CAK7LNARvyxzJa9CG-4uSoE7asdHp=Cbeh71_13dmuP8zMJtqSA@mail.gmail.com> (raw)
In-Reply-To: <20190730164959.GA129059@archlinux-threadripper>

On Wed, Jul 31, 2019 at 1:50 AM Nathan Chancellor
<natechancellor@gmail.com> wrote:
>
> On Tue, Jul 30, 2019 at 09:48:03AM -0700, Stephen Boyd wrote:
> > If the particular version of clang a user has doesn't enable
> > -Werror=unknown-warning-option by default, even though it is the
> > default[1], then make sure to pass the option to the Kconfig cc-option
> > command so that testing options from Kconfig files works properly.
> > Otherwise, depending on the default values setup in the clang toolchain
> > we will silently assume options such as -Wmaybe-uninitialized are
> > supported by clang, when they really aren't.
> >
> > A compilation issue only started happening for me once commit
> > 589834b3a009 ("kbuild: Add -Werror=unknown-warning-option to
> > CLANG_FLAGS") was applied on top of commit b303c6df80c9 ("kbuild:
> > compute false-positive -Wmaybe-uninitialized cases in Kconfig"). This
> > leads kbuild to try and test for the existence of the
> > -Wmaybe-uninitialized flag with the cc-option command in
> > scripts/Kconfig.include, and it doesn't see an error returned from the
> > option test so it sets the config value to Y. Then the Makefile tries to
> > pass the unknown option on the command line and
> > -Werror=unknown-warning-option catches the invalid option and breaks the
> > build. Before commit 589834b3a009 ("kbuild: Add
> > -Werror=unknown-warning-option to CLANG_FLAGS") the build works fine,
> > but any cc-option test of a warning option in Kconfig files silently
> > evaluates to true, even if the warning option flag isn't supported on
> > clang.
> >
> > Note: This doesn't change cc-option usages in Makefiles because those
> > use a different rule that includes KBUILD_CFLAGS by default (see the
> > __cc-option command in scripts/Kbuild.incluide). The KBUILD_CFLAGS
> > variable already has the -Werror=unknown-warning-option flag set. Thanks
> > to Doug for pointing out the different rule.
> >
> > [1] https://clang.llvm.org/docs/DiagnosticsReference.html#wunknown-warning-option
> > Cc: Peter Smith <peter.smith@linaro.org>
> > Cc: Nathan Chancellor <natechancellor@gmail.com>
> > Cc: Nick Desaulniers <ndesaulniers@google.com>
> > Cc: Douglas Anderson <dianders@chromium.org>
> > Signed-off-by: Stephen Boyd <swboyd@chromium.org>
>
> Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>
>
> > ---
> >  Makefile                | 1 +
> >  scripts/Kconfig.include | 2 +-
> >  2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/Makefile b/Makefile
> > index 9be5834073f8..517d0a3f6539 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -536,6 +536,7 @@ KBUILD_AFLAGS     += $(CLANG_FLAGS)
> >  export CLANG_FLAGS
> >  endif
> >
> > +
>
> Not sure it's worth sending a v4 for but I don't think this should be
> there.


I will remove it when I apply this.



-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2019-07-30 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 16:48 [PATCH v3] kbuild: Check for unknown options with cc-option usage in Kconfig and clang Stephen Boyd
2019-07-30 16:49 ` Nathan Chancellor
2019-07-30 16:51   ` Masahiro Yamada [this message]
2019-08-01  2:56     ` Masahiro Yamada

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='CAK7LNARvyxzJa9CG-4uSoE7asdHp=Cbeh71_13dmuP8zMJtqSA@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=dianders@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=peter.smith@linaro.org \
    --cc=swboyd@chromium.org \
    /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).