From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: Nathan Huckleberry <nhuck@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Roeder <tmroeder@google.com>,
clang-built-linux@googlegroups.com,
Masahiro Yamada <masahiroy@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] kbuild: clang-tidy
Date: Thu, 13 Aug 2020 02:39:55 +0900 [thread overview]
Message-ID: <20200812173958.2307251-1-masahiroy@kernel.org> (raw)
I improved gen_compile_commands.py in the first two patches,
then rebased Nathan's v7 [1] on top of them.
To save time, I modified the Makefile part.
No change for run-clang-tools.py
I am not sure if the new directory, scripts/clang-tools/,
is worth creating only for 2 files, but I do not have
a strong opinion about it.
"make clang-tidy" should work in-tree build,
out-of-tree build (O=), and external module build (M=).
Tests and reviews are appreciated.
"make clang-tidy" worked for me.
masahiro@oscar:~/workspace/linux-kbuild$ make -j24 CC=clang clang-tidy
DESCEND objtool
CALL scripts/atomic/check-atomics.sh
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
GEN compile_commands.json
CHECK compile_commands.json
But "make clang-analyzer" just sprinkled the following error:
Error: no checks enabled.
USAGE: clang-tidy [options] <source0> [... <sourceN>]
I built clang-tidy from the latest source.
I had no idea how to make it work...
[1] https://patchwork.kernel.org/patch/11687833/
Masahiro Yamada (2):
gen_compile_commands: parse only the first line of .*.cmd files
gen_compile_commands: wire up build rule to Makefile
Nathan Huckleberry (1):
Makefile: Add clang-tidy and static analyzer support to makefile
MAINTAINERS | 1 +
Makefile | 45 +++++-
scripts/clang-tools/gen_compile_commands.py | 117 +++++++++++++++
scripts/clang-tools/run-clang-tools.py | 74 ++++++++++
scripts/gen_compile_commands.py | 151 --------------------
5 files changed, 233 insertions(+), 155 deletions(-)
create mode 100755 scripts/clang-tools/gen_compile_commands.py
create mode 100755 scripts/clang-tools/run-clang-tools.py
delete mode 100755 scripts/gen_compile_commands.py
--
2.25.1
next reply other threads:[~2020-08-12 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 17:39 Masahiro Yamada [this message]
2020-08-12 17:39 ` [PATCH 1/3] gen_compile_commands: parse only the first line of .*.cmd files Masahiro Yamada
2020-08-12 21:52 ` Nick Desaulniers
2020-08-12 17:39 ` [PATCH 2/3] gen_compile_commands: wire up build rule to Makefile Masahiro Yamada
2020-08-12 22:30 ` Nick Desaulniers
2020-08-13 17:10 ` Masahiro Yamada
2020-08-19 4:29 ` Masahiro Yamada
2020-08-20 2:29 ` Nick Desaulniers
2020-08-12 17:39 ` [PATCH 3/3] Makefile: Add clang-tidy and static analyzer support to makefile Masahiro Yamada
2020-08-12 19:56 ` [PATCH 0/3] kbuild: clang-tidy Nathan Huckleberry
2020-08-12 22:52 ` Nick Desaulniers
2020-08-12 22:55 ` Nick Desaulniers
2020-08-13 0:50 ` Nathan Chancellor
2020-08-13 0:57 ` Masahiro Yamada
2020-08-13 1:34 ` 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=20200812173958.2307251-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=nhuck@google.com \
--cc=robh@kernel.org \
--cc=tmroeder@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 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).