[Dependency Scanning] Include initial PCM arguments on Clang module dependency details

Doing so will allow clients to know which Swift-specific PCM arguments are already captured from the scan that first discovered this module.
SwiftDriver, in particular, will be able to use this information to avoid re-scanning a given Clang module if the initial scan was sufficient for all possible sets of PCM arguments on Swift modules that depend on said Clang module.
This commit is contained in:
Artem Chikin
2021-09-22 11:34:02 -07:00
parent e460a7db84
commit 6176657285
10 changed files with 62 additions and 17 deletions

View File

@@ -74,6 +74,7 @@ void swiftscan_dependency_info_details_dispose(
swiftscan_string_dispose(details_impl->clang_details.module_map_path);
swiftscan_string_dispose(details_impl->clang_details.context_hash);
swiftscan_string_set_dispose(details_impl->clang_details.command_line);
swiftscan_string_set_dispose(details_impl->clang_details.captured_pcm_args);
break;
}
delete details_impl;
@@ -346,6 +347,11 @@ swiftscan_clang_detail_get_command_line(swiftscan_module_details_t details) {
return details->clang_details.command_line;
}
swiftscan_string_set_t *
swiftscan_clang_detail_get_captured_pcm_args(swiftscan_module_details_t details) {
return details->clang_details.captured_pcm_args;
}
//=== Batch Scan Input Functions ------------------------------------------===//
swiftscan_batch_scan_input_t *swiftscan_batch_scan_input_create() {