From: Nathan Chancellor <nathan@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gen_compile_commands: prune some directories
Date: Thu, 11 Feb 2021 10:19:08 -0700 [thread overview]
Message-ID: <20210211171908.GA3820685@ubuntu-m3-large-x86> (raw)
In-Reply-To: <20210211161154.3892836-1-masahiroy@kernel.org>
On Fri, Feb 12, 2021 at 01:11:54AM +0900, Masahiro Yamada wrote:
> If directories are passed to gen_compile_commands.py, os.walk() traverses
> all the subdirectories to search for .cmd files, but we know some of them
> are not worth traversing.
>
> Use the 'topdown' parameter of os.walk to prune them.
>
> Documentation about the 'topdown' option of os.walk:
> When topdown is True, the caller can modify the dirnames list
> in-place (perhaps using del or slice assignment), and walk() will
> only recurse into the subdirectories whose names remain in dirnames;
> this can be used to prune the search, impose a specific order of
> visiting, or even to inform walk() about directories the caller
> creates or renames before it resumes walk() again. Modifying
> dirnames when topdown is False has no effect on the behavior of
> the walk, because in bottom-up mode the directories in dirnames
> are generated before dirpath itself is generated.
>
> This commit prunes four directories, .git, Documentation, include, and
> tools.
>
> The first three do not contain any C files. My main motivation is the
> last one, tools/ directory.
>
> Commit 6ca4c6d25949 ("gen_compile_commands: do not support .cmd files
> under tools/ directory") stopped supporting the tools/ directory.
> The current code no longer picks up .cmd files from the tools/
> directory.
>
> If you run:
>
> ./scripts/clang-tools/gen_compile_commands.py --log_level=INFO
>
> then, you will see several "File ... not found" log messages.
>
> This is expected, and I do not want to support the tools/ directory.
> However, without an explicit comment "do not support tools/", somebody
> might try to get it back. Clarify this.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Sorry, I did not realize that gen_compile_commands.py did not intend to
support. I was only looking at the history for the current location, not
the former one of scripts/gen_compile_commands.py.
Acked-by: Nathan Chancellor <nathan@kernel.org>
> ---
>
> scripts/clang-tools/gen_compile_commands.py | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/clang-tools/gen_compile_commands.py b/scripts/clang-tools/gen_compile_commands.py
> index 19963708bcf8..eb5faefbdf74 100755
> --- a/scripts/clang-tools/gen_compile_commands.py
> +++ b/scripts/clang-tools/gen_compile_commands.py
> @@ -20,7 +20,9 @@ _DEFAULT_LOG_LEVEL = 'WARNING'
> _FILENAME_PATTERN = r'^\..*\.cmd$'
> _LINE_PATTERN = r'^cmd_[^ ]*\.o := (.* )([^ ]*\.c)$'
> _VALID_LOG_LEVELS = ['DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL']
> -
> +# The tools/ directory adopts a different build system, and produces .cmd
> +# files in a different format. Do not support it.
> +_EXCLUDE_DIRS = ['.git', 'Documentation', 'include', 'tools']
>
> def parse_arguments():
> """Sets up and parses command-line arguments.
> @@ -80,8 +82,14 @@ def cmdfiles_in_dir(directory):
> """
>
> filename_matcher = re.compile(_FILENAME_PATTERN)
> + exclude_dirs = [ os.path.join(directory, d) for d in _EXCLUDE_DIRS ]
> +
> + for dirpath, dirnames, filenames in os.walk(directory, topdown=True):
> + # Prune unwanted directories.
> + if dirpath in exclude_dirs:
> + dirnames[:] = []
> + continue
>
> - for dirpath, _, filenames in os.walk(directory):
> for filename in filenames:
> if filename_matcher.match(filename):
> yield os.path.join(dirpath, filename)
> --
> 2.27.0
>
next prev parent reply other threads:[~2021-02-11 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 16:11 Masahiro Yamada
2021-02-11 17:19 ` Nathan Chancellor [this message]
2021-02-16 6:40 ` 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=20210211171908.GA3820685@ubuntu-m3-large-x86 \
--to=nathan@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®