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>,
Michal Marek <michal.lkml@markovi.net>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 00/10] kbuild: clang-tidy
Date: Sat, 22 Aug 2020 23:56:08 +0900 [thread overview]
Message-ID: <20200822145618.1222514-1-masahiroy@kernel.org> (raw)
I improved gen_compile_commands.py,
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
"make clang-tidy" should work in-tree build,
out-of-tree build (O=), and external module build (M=).
V3:
Fix minor mistakes pointed out by Nick
Add a new patch (09/10) to remove the warning about
too few .cmd files.
V2:
Keep the previous work-flow.
You can still manually run scripts/gen_compile_commands.json
'make compile_commands.json' or 'make clang-tidy' is handier
for most cases. As Nick noted, there is 3 % loss of the coverage.
If you need the full compilation database that covers all the
compiled C files, please run the script manually.
[1] https://patchwork.kernel.org/patch/11687833/
Masahiro Yamada (9):
gen_compile_commands: parse only the first line of .*.cmd files
gen_compile_commands: use choices for --log_levels option
gen_compile_commands: do not support .cmd files under tools/ directory
gen_compile_commands: reword the help message of -d option
gen_compile_commands: make -o option independent of -d option
gen_compile_commands: move directory walk to a generator function
gen_compile_commands: support *.o, *.a, modules.order in positional
argument
kbuild: wire up the build rule of compile_commands.json to Makefile
gen_compile_commands: remove the warning about too few .cmd files
Nathan Huckleberry (1):
Makefile: Add clang-tidy and static analyzer support to makefile
MAINTAINERS | 1 +
Makefile | 45 +++-
scripts/clang-tools/gen_compile_commands.py | 236 ++++++++++++++++++++
scripts/clang-tools/run-clang-tools.py | 74 ++++++
scripts/gen_compile_commands.py | 151 -------------
5 files changed, 352 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-22 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 14:56 Masahiro Yamada [this message]
2020-08-22 14:56 ` [PATCH v3 01/10] gen_compile_commands: parse only the first line of .*.cmd files Masahiro Yamada
2020-08-22 14:56 ` [PATCH v3 02/10] gen_compile_commands: use choices for --log_levels option Masahiro Yamada
2020-08-22 14:56 ` [PATCH v3 03/10] gen_compile_commands: do not support .cmd files under tools/ directory Masahiro Yamada
2020-08-22 14:56 ` [PATCH v3 04/10] gen_compile_commands: reword the help message of -d option Masahiro Yamada
2020-08-22 14:56 ` [PATCH v3 05/10] gen_compile_commands: make -o option independent " Masahiro Yamada
2020-08-22 14:56 ` [PATCH v3 06/10] gen_compile_commands: move directory walk to a generator function Masahiro Yamada
2020-08-22 14:56 ` [PATCH v3 07/10] gen_compile_commands: support *.o, *.a, modules.order in positional argument Masahiro Yamada
2020-08-23 0:40 ` Nick Desaulniers
2020-08-22 14:56 ` [PATCH v3 08/10] kbuild: wire up the build rule of compile_commands.json to Makefile Masahiro Yamada
2020-08-22 14:56 ` [PATCH v3 09/10] gen_compile_commands: remove the warning about too few .cmd files Masahiro Yamada
2020-08-23 0:47 ` Nick Desaulniers
2020-08-22 14:56 ` [PATCH v3 10/10] Makefile: Add clang-tidy and static analyzer support to makefile Masahiro Yamada
2020-08-26 13:27 ` [PATCH v3 00/10] kbuild: clang-tidy 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=20200822145618.1222514-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=nhuck@google.com \
--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).