en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/ClangScanDeps/Inputs/modules-pch/module.modulemap#4629554f [clang][deps] Handle modular dependencies present in PCHWhen a translation unit uses a PCH and imports the same modules as the PCH, we'd prefer to resolve to those modules instead of inventing new modules and reporting them as modular dependencies. Since the PCH modules have already been built nudge the compiler to reuse them when deciding whether to build a new module and don't report them as regular modular dependencies.Depends on D103524 & D103802.Reviewed By: dexonsmithDifferential Revision: https://reviews.llvm.org/D103526 List of files: /llvm-project-15.0.7/clang/test/ClangScanDeps/Inputs/modules-pch/module.modulemap Mon, 14 Jun 2021 09:30:26 +0000 Jan Svoboda <jan_svoboda@apple.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/ClangScanDeps/Inputs/modules-pch/module.modulemap#de07b1e8 [clang][deps] Support object filesWhen a project uses PCH with explicit modules, the build will look like this:1. scan PCH dependencies2. explicitly build PCH3. scan TU dependencies4. explicitly build TUStep 2 produces an object file for the PCH, which the dependency scanner needs to read in step 3. This patch adds support for this.The `clang-scan-deps` invocation in the attached test would fail without this change.Depends on D103516.Reviewed By: BigcheeseDifferential Revision: https://reviews.llvm.org/D103519 List of files: /llvm-project-15.0.7/clang/test/ClangScanDeps/Inputs/modules-pch/module.modulemap Wed, 02 Jun 2021 12:49:14 +0000 Jan Svoboda <jan_svoboda@apple.com>