diff options
author | Masahiro Yamada <masahiroy@kernel.org> | 2020-06-14 17:43:40 +0300 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2020-06-17 04:20:21 +0300 |
commit | f2f02ebd8f3833626642688b2d2c6a7b3c141fa9 (patch) | |
tree | 5f83d2cb665a34e5748ed26a9affe67e4a4cff6c /arch | |
parent | 7b16994437c7359832dd51d66c5c387995a91438 (diff) | |
download | linux-f2f02ebd8f3833626642688b2d2c6a7b3c141fa9.tar.xz |
kbuild: improve cc-option to clean up all temporary files
When cc-option and friends evaluate compiler flags, the temporary file
$$TMP is created as an output object, and automatically cleaned up.
The actual file path of $$TMP is .<pid>.tmp, here <pid> is the process
ID of $(shell ...) invoked from cc-option. (Please note $$$$ is the
escape sequence of $$).
Such garbage files are cleaned up in most cases, but some compiler flags
create additional output files.
For example, -gsplit-dwarf creates a .dwo file.
When CONFIG_DEBUG_INFO_SPLIT=y, you will see a bunch of .<pid>.dwo files
left in the top of build directories. You may not notice them unless you
do 'ls -a', but the garbage files will increase every time you run 'make'.
This commit changes the temporary object path to .tmp_<pid>/tmp, and
removes .tmp_<pid> directory when exiting. Separate build artifacts such
as *.dwo will be cleaned up all together because their file paths are
usually determined based on the base name of the object.
Another example is -ftest-coverage, which outputs the coverage data into
<base-name-of-object>.gcno
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions