From: Daniel Thompson <daniel.thompson@linaro.org>
To: Nathan Chancellor <nathan@kernel.org>, Tom Rix <trix@redhat.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kbuild@vger.kernel.org, llvm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] Makefile: Enable clang-tidy and clang-analyzer for gcc builds
Date: Tue, 28 Jun 2022 13:27:40 +0100 [thread overview]
Message-ID: <20220628122741.93641-3-daniel.thompson@linaro.org> (raw)
In-Reply-To: <20220628122741.93641-1-daniel.thompson@linaro.org>
It is now possible use clang-tidy and clang-analyzer even if your primary
compiler is gcc. Remove the checks that prevent gcc builds from using
these tools.
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
---
Makefile | 6 ------
1 file changed, 6 deletions(-)
diff --git a/Makefile b/Makefile
index 9ea6867aaf9c..0afef56d8203 100644
--- a/Makefile
+++ b/Makefile
@@ -1901,17 +1901,11 @@ targets += $(extmod_prefix)compile_commands.json
PHONY += clang-tidy clang-analyzer
-ifdef CONFIG_CC_IS_CLANG
quiet_cmd_clang_tools = CHECK $<
cmd_clang_tools = $(PYTHON3) $(srctree)/scripts/clang-tools/run-clang-tools.py $@ $<
clang-tidy clang-analyzer: $(extmod_prefix)compile_commands.json
$(call cmd,clang_tools)
-else
-clang-tidy clang-analyzer:
- @echo "$@ requires CC=clang" >&2
- @false
-endif
# Scripts to check various things for consistency
# ---------------------------------------------------------------------------
--
2.35.1
next prev parent reply other threads:[~2022-06-28 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:27 [PATCH 0/2] Enable clang tools for kernels build using gcc Daniel Thompson
2022-06-28 12:27 ` [PATCH 1/2] clang-tools: Generate clang compatible output even with gcc builds Daniel Thompson
2022-06-28 18:35 ` Nick Desaulniers
2022-06-28 12:27 ` Daniel Thompson [this message]
2022-06-28 13:19 ` [PATCH 0/2] Enable clang tools for kernels build using gcc Tom Rix
2022-06-28 15:15 ` Daniel Thompson
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=20220628122741.93641-3-daniel.thompson@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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