John Hubbard a4ab14e1d8 gen_compile_commands: handle multiple lines per .mod file ...

scripts/clang-tools/gen_compile_commands.py incorrectly assumes that
each .mod file only contains one line. That assumption was correct when
the script was originally created, but commit 9413e76405 ("kbuild:
split the second line of *.mod into *.usyms") changed the .mod file
format so that there is one entry per line, and potentially many lines.

The problem can be reproduced by using Kbuild to generate
compile_commands.json, like this:

    make CC=clang compile_commands.json

In many cases, the problem might be overlooked because many subsystems
only have one line anyway. However, in some subsystems (Nouveau, with
762 entries, is a notable example) it results in skipping most of the
subsystem.

Fix this by fully processing each .mod file.

Fixes: 9413e76405 ("kbuild: split the second line of *.mod into *.usyms")
Signed-off-by: John Hubbard <[email protected]>
Reviewed-by: Nick Desaulniers <[email protected]>
Signed-off-by: Masahiro Yamada <[email protected]>

2022-06-29 11:43:13 +09:00

..

gen_compile_commands.py

gen_compile_commands: handle multiple lines per .mod file

2022-06-29 11:43:13 +09:00

run-clang-tools.py

scripts/clang-tools: switch explicitly to Python 3

2021-02-03 09:01:08 +09:00