Add handling of the -nostdlibinc option to ccc-analyzer

[ziqingluo-90]

Compiler options recognizable to ccc-analyzer are stored in maps. An option missing in the map will be dropped by ccc-analyzer. This causes a build error in one of our projects that only happens in scan-build but not regular build, because ccc-analyzer do not recognize -nostdlibinc.

This commit adds the option to the map.

[llvmbot]

@llvm/pr-subscribers-clang-static-analyzer-1

@llvm/pr-subscribers-clang

Author: Ziqing Luo (ziqingluo-90)

Changes

Compiler options recognizable to ccc-analyzer are stored in maps. An option missing in the map will be dropped by ccc-analyzer. This causes a build error in one of our projects that only happens in scan-build but not regular build, because ccc-analyzer do not recognize -nostdlibinc.

This commit adds the option to the map.

---

Full diff: https://github.com/llvm/llvm-project/pull/88017.diff

1 Files Affected:

• (modified) clang/tools/scan-build/libexec/ccc-analyzer (+1)

diff --git a/clang/tools/scan-build/libexec/ccc-analyzer b/clang/tools/scan-build/libexec/ccc-analyzer
index 60796a543fcd06..c5588814e8f0de 100755
--- a/clang/tools/scan-build/libexec/ccc-analyzer
+++ b/clang/tools/scan-build/libexec/ccc-analyzer
@@ -361,6 +361,7 @@ sub Analyze {
 
 my %CompileOptionMap = (
   '-nostdinc' => 0,
+  '-nostdlibinc' => 0,
   '-include' => 1,
   '-idirafter' => 1,
   '-imacros' => 1,

[haoNoQ]

I never realized that scan-build makes a "short list" of flags to pass through and throws away the rest. This is terrifying. It only works because most compiler flags are recognized because they're prefixed with -f, -W, etc.; but it's fascinating that it even works.

This may be testable; we've recently started adding tests for scan-build. But you'll have to see how -nostdlibinc is tested in general, and then see if you can combine the two tricks.