llvm-project.git/clang/test/ClangScanDeps/modules-implementation-module-map.c, branch main Unnamed repository; edit this file 'description' to name the repository. [clang][deps] Add module map describing compiled module to file dependencies. (#160226) 2025-11-20T04:17:43+00:00 Volodymyr Sapsai vsapsai@apple.com 2025-11-20T04:17:43+00:00 b39a9db3abc7abfa033a728ef29b5e5d3beb1cb5 When we add the module map describing the compiled module to the command line, add it to the file dependencies as well. Discovered while working on reproducers where a command line input was missing in the captured files as it wasn't considered a dependency. 
When we add the module map describing the compiled module to the command
line, add it to the file dependencies as well.

Discovered while working on reproducers where a command line input was
missing in the captured files as it wasn't considered a dependency.
 [clang-scan-deps] Infer the tool locations from PATH (#108539) 2024-09-13T20:18:10+00:00 Martin Storsjö martin@martin.st 2024-09-13T20:18:10+00:00 a26ec542371652e1d774696e90016fd5b0b1c191 This allows the clang driver to know which tool is meant to be executed, which allows the clang driver to load the right clang config files, and allows clang to find colocated sysroots. This makes sure that doing `clang-scan-deps -- <tool> ...` looks up things in the same way as if one just would execute `<tool> ...`, when `<tool>` isn't an absolute or relative path. 
This allows the clang driver to know which tool is meant to be executed,
which allows the clang driver to load the right clang config files, and
allows clang to find colocated sysroots.

This makes sure that doing `clang-scan-deps -- <tool> ...` looks up
things in the same way as if one just would execute `<tool> ...`, when
`<tool>` isn't an absolute or relative path.
 [clang][deps] Prevent emitting diagnostics outside of source file 2022-10-11T22:57:20+00:00 Jan Svoboda jan_svoboda@apple.com 2022-10-11T22:38:48+00:00 c1c72302fe4553a39be37b5c310d046975e55019 The dependency scanner needs to report the module map file describing the module whose implementation is being compiled (see D134222). However, calling `Preprocessor::getCurrentModuleImplementation()` in the scanner might cause a diagnostic during module map parsing and emitting a diagnostic without being "in" a source file is illegal (e.g. in `TextDiagnosticPrinter`). This patch ensures the module map parse is triggered while the compiler is still "in" a source file, avoiding the failure case. Reviewed By: Bigcheese Differential Revision: https://reviews.llvm.org/D135637 
The dependency scanner needs to report the module map file describing the module whose implementation is being compiled (see D134222). However, calling `Preprocessor::getCurrentModuleImplementation()` in the scanner might cause a diagnostic during module map parsing and emitting a diagnostic without being "in" a source file is illegal (e.g. in `TextDiagnosticPrinter`). This patch ensures the module map parse is triggered while the compiler is still "in" a source file, avoiding the failure case.

Reviewed By: Bigcheese

Differential Revision: https://reviews.llvm.org/D135637