On Sat, Aug 1, 2020 at 12:23 PM Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx> wrote: > > Hi Nathan, Hi Nick, > > I have been busy with other topics around the kernel and static analysis; > but then, I read clang and static analysis in my mailbox in this patch. > > So, I thought let me give this patch a try on the weekend. > > I applied the patch on next-2020729; that worked. > > Then: > $ make clang-tidy > scripts/clang-tools/Makefile.clang-tools:13: *** clang-tidy requires > CC=clang. Stop. > > Okay, that is a good and clear error message. > > Then: > > $ make CC=clang-10 defconfig > $ make CC=clang-10 clang-tidy > > python3 scripts/clang-tools/gen_compile_commands.py > WARNING: Found 8 entries. Have you compiled the kernel? > python3 scripts/clang-tools/run-clang-tools.py clang-tidy > compile_commands.json > > Then actually an error in clang-tidy. > Error: no checks enabled. > USAGE: clang-tidy [options] <source0> [... <sourceN>] > ... > > I will get to that later how I fixed that for my setup. > > Okay, good, that is clear... I need to compile it first, got it. Hi Lukas, Thank you so much for taking the time to apply the patch and help test it. For the case of not doing a build first: gen_compile_commands.py parses the .*.d files to build the compilation database and warns if not many were found. I think it might be interesting for it to just invoke a build if it sees that, or maybe for the clang-tidy and clang-analyzer targets to somehow invoke the default make target. The issue there might be that you need to invoke `make clang-tidy` with `make CC=clang LD=ld.lld ... clang-tidy` in order to trigger a build successfully. Also, I wonder if gen_compile_commands.py should set a return code in that case so that callers can handle such an exceptional case? In that case, I'd consider that a papercut or potential improvement to scripts/get_compile_commands.py orthogonal to this patch. > > $ make CC=clang-10 > $ make CC=clang-10 clang-tidy > > Okay, I run except for the fix I needed. > > Where is the output from clang-tidy? > > It prints: > > python3 scripts/clang-tools/gen_compile_commands.py > python3 scripts/clang-tools/run-clang-tools.py clang-tidy compile_commands.json > > That is it. Does that mean 0 warnings, or where do I find the output? > The script suggests it should be in stderr once all the parallel runs > collected it, right? > > I was confused; maybe a short summary output might help here. I was also caught by this; for x86 defconfig, the kernel is actually clean of instances of linuxkernel-* clang-tidy checks (there was also an issue with the CWD for x86 in v6, but was resolved in v7 of this patch). I had to add a case that should fail to make clang-tidy have output, and the check only checks for unchecked "ERR_PTR", "PTR_ERR", "IS_ERR", "IS_ERR_OR_NULL", "ERR_CAST", "PTR_ERR_OR_ZERO". (Documentation for that should be improved.) So if you add a function that just constructs an `ERR_PTR(0)` and call it from code that gets compiled in, then you'll start to see warnings from clang-tidy for x86 defconfig. For aarch64 and arm, you'll see there are some unchecked cases that look like low hanging fruit to fix. It probably can be improved to note that there was no output, but that will require more machinery to track how much output there was. I'd prefer to follow up with additional polish on top of this once this lands. > > Then, I ran > > $ make CC=clang-10 clang-analyzer > > And I see a lot of warnings... I guess that is intended. > > There is a lot of: > > Suppressed XX warnings (XX in non-user code). > Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well. > > To an outsider, it is unclear if that is intended or if the tool is broken > in this setup. > > Is there are way to silent that meta-warning? Or is my setup broken? See also my comment about disabling the clang-diagnostic-* analyzer checks. We haven't had time to sort out the cause of them yet, and for now they just look like noise. > > In summary, it is pretty clear how to run clang-tidy and clang-analyzer > and it was a pretty smooth experience, even with no documentation at hand. > > It was fun for me. Keep up the good work! > > Just one issue... see below. > > > + p = subprocess.run(["clang-tidy", "-p", args.path, checks, entry["file"]], > > You hardcoded here: clang-tidy > > But in my Ubuntu 18.04 setup, I got multiple versions of clang and > clang-tidy installed; yeah, maybe my setup is broken, but maybe those from > others are similar. > > When I run: > > make CC=clang-10 clang-tidy > > it picks up the "wrong" clang-tidy version... > > My setup is: > > $ which clang-tidy > /usr/bin/clang-tidy > > $ which clang-tidy-10 > /usr/bin/clang-tidy-10 > > $ clang-tidy --version > LLVM (http://llvm.org/): > LLVM version 6.0.0 > > Optimized build. > Default target: x86_64-pc-linux-gnu > Host CPU: znver1 > > $ clang-tidy-10 --version > LLVM (http://llvm.org/): > LLVM version 10.0.1 > > Optimized build. > Default target: x86_64-pc-linux-gnu > Host CPU: znver1 > > When I run make CC=clang-10 clang-tidy, I would expect it to use > clang-tidy-10, not clang-tidy. (clang-tidy errors just because it is too > old; I guess it does have the linuxkernel-* options.) > > Now, I cannot fix that without touching your script. There is no way I can > tell the build target to use clang-tidy-10. > > With a quick touch: > > - p = subprocess.run(["clang-tidy", "-p", args.path, checks, entry["file"]], > + p = subprocess.run(["clang-tidy-10", "-p", args.path, checks, entry["file"]], > > I got it to work. > > Maybe you have a good idea how to get make clang-tidy to pick > up the intended version without touching the python script itself? > > It is a minor issue, but it would be nice if that setting would work > somehow. Ah right, sorry, I tend to forget about the use case of having multiple versions of clang installed. I think the best approach here might be for the user (you, in this case) to ensure that list of PATHs in the path list has the path to the intended version of clang-tidy you'd like to run listed before others. That is similar to the recommendation for the LLVM=1 patch set. ie. commit a0d1c951ef08e ("kbuild: support LLVM=1 to switch the default tools to Clang/LLVM") specifically this part of the commit message: > the suffixed versions in /usr/bin/ are symlinks to binaries in > /usr/lib/llvm-#/bin/, so this can also be handled by PATH. If `clang-tidy` on your system points to an old version of clang-tidy, it may be worthwhile to uninstall the old version, and update the symlink to point to a newer version. That may be simpler than trying to support invoking `make clang-tidy` for arbitrary versions or binary names of clang-tidy. I can understand having multiple versions of a compiler installed for quickly checking compatibility (though these days I prefer godbolt.org for that) or if a particular codebase is stuck on an old version of a toolchain for whatever reason; but having multiple versions of clang-tidy installed and supporting all of them is a little harder to justify. -- Thanks, ~Nick Desaulniers
