From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v2 2/2] MIPS: Loongson{2ef,64}: Wrap -mno-branch-likely with cc-option
Date: Mon, 7 Feb 2022 18:36:09 +0100 [thread overview]
Message-ID: <20220207173609.GC16822@alpha.franken.de> (raw)
In-Reply-To: <20220125221925.3547683-2-nathan@kernel.org>
On Tue, Jan 25, 2022 at 03:19:25PM -0700, Nathan Chancellor wrote:
> This flag is not supported by clang, which results in a warning:
>
> clang-14: warning: argument unused during compilation: '-mno-branch-likely' [-Wunused-command-line-argument]
>
> This breaks cc-option, which adds -Werror to make this warning fatal and
> catch flags that are not supported.
>
> Wrap this flag in cc-option so that it does not cause cc-option to fail,
> which can cause randconfigs to be really noisy, due to warnings not
> getting disabled that should be.
>
> Additionally, move the cc-option check to Kconfig so that the check is
> done at configuration time, rather than build time, as builds with no
> configuration change will be quicker because the cc-option call will not
> need to happen in those instances.
>
> Suggested-by: Nick Desaulniers <ndesaulniers@google.com>
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
>
> v1 -> v2: https://lore.kernel.org/r/20220120214001.1879469-2-nathan@kernel.org/
>
> * Move cc-option call to Kconfig (Nick).
> * Also apply to loongson2ef, even though this will not currently build
> with clang.
>
> arch/mips/Kconfig | 4 ++++
> arch/mips/loongson2ef/Platform | 3 ++-
> arch/mips/loongson64/Platform | 3 ++-
> 3 files changed, 8 insertions(+), 2 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2022-02-07 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 22:19 [PATCH v2 1/2] MIPS: Loongson64: Clean up use of cc-ifversion Nathan Chancellor
2022-01-25 22:19 ` [PATCH v2 2/2] MIPS: Loongson{2ef,64}: Wrap -mno-branch-likely with cc-option Nathan Chancellor
2022-02-07 17:36 ` Thomas Bogendoerfer [this message]
2022-02-07 17:35 ` [PATCH v2 1/2] MIPS: Loongson64: Clean up use of cc-ifversion Thomas Bogendoerfer
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=20220207173609.GC16822@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.