Buildresult: kbuild/ppc64le_defconfig/powerpc-gcc5 built on Feb 16 2021, 18:21

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Feb 16 2021, 18:21
Duration:	0:04:02.770265
Builder:	blade4b
Revision:	gen_compile_commands: prune some directories (`fb9e9b6e96e2869b670ecd200219920968838cfd)`
Target:	kbuild/ppc64le_defconfig/powerpc-gcc5
Branch:	kbuild
Compiler:	powerpc-gcc5 (powerpc64-linux-gcc (GCC) 5.5.0 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	ppc64le_defconfig (download)
Log:	Download original No warnings found in log. Full Log # git rev-parse -q --verify fb9e9b6e96e2869b670ecd200219920968838cfd^{commit} fb9e9b6e96e2869b670ecd200219920968838cfd already have revision, skipping fetch # git checkout -q -f -B kisskb fb9e9b6e96e2869b670ecd200219920968838cfd # git clean -qxdf # < git log -1 # commit fb9e9b6e96e2869b670ecd200219920968838cfd # Author: Masahiro Yamada <masahiroy@kernel.org> # Date: Fri Feb 12 01:11:54 2021 +0900 # # gen_compile_commands: prune some directories # # 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> # Acked-by: Nathan Chancellor <nathan@kernel.org> # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version # < git log --format=%s --max-count=1 fb9e9b6e96e2869b670ecd200219920968838cfd # < make -s -j 24 ARCH=powerpc O=/kisskb/build/kbuild_ppc64le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- ppc64le_defconfig # < make -s -j 24 ARCH=powerpc O=/kisskb/build/kbuild_ppc64le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- help # make -s -j 24 ARCH=powerpc O=/kisskb/build/kbuild_ppc64le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- olddefconfig # make -s -j 24 ARCH=powerpc O=/kisskb/build/kbuild_ppc64le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- Completed OK # rm -rf /kisskb/build/kbuild_ppc64le_defconfig_powerpc-gcc5 # Build took: 0:04:02.770265

© Michael Ellerman 2006-2018.