aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorCyndy Ishida <cyndy_ishida@apple.com>2025-04-29 08:38:33 -0700
committerGitHub <noreply@github.com>2025-04-29 08:38:33 -0700
commitbd3dde0f871cd71a797ba5da3070fa3ddbc48828 (patch)
tree439b81ab195523a3b1c2cd875c5d6eed9f8b6460 /clang/lib/Frontend/CompilerInvocation.cpp
parent55287705691ab42e5b15d2b2847a22aaa3b99e84 (diff)
downloadllvm-bd3dde0f871cd71a797ba5da3070fa3ddbc48828.zip
llvm-bd3dde0f871cd71a797ba5da3070fa3ddbc48828.tar.gz
llvm-bd3dde0f871cd71a797ba5da3070fa3ddbc48828.tar.bz2
[clang][Modules] Diagnose mismatching pcm dependencies in explicit buiilds (#137068)
In an explicit build, the dependency scanner generates invocations with dependencies to module files to use during compilation. The pcm's passed in the invocations should match the ones that were imported by other modules that share the same dependencies. We have seen bugs caused from incorrect invocations that mismatch which module file to load. When this happens report it as a warning, to help with investigations, as that should never occur in a well behaved build scheduled from the dependency scanner. The warning flag is off by default.
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions