diff options
| author | Jan Svoboda <jan_svoboda@apple.com> | 2021-10-12 09:34:43 +0200 |
|---|---|---|
| committer | Jan Svoboda <jan_svoboda@apple.com> | 2021-10-12 12:20:55 +0200 |
| commit | 444513510999e4c1ea23253654196793834d53bf (patch) | |
| tree | 0533b14af4e4901deaa22b6ebbc3c4c94942d4b8 /lldb/test/API/lua_api/TestProcessAPI.lua | |
| parent | f4c1258d5633fcf06385ff3fd1f4bf57ab971964 (diff) | |
[clang][lex] Remark on search path usage
For dependency scanning, it would be useful to collect header search paths (provided on command-line via `-I` and friends) that were actually used during preprocessing. This patch adds that feature to `HeaderSearch` along with a new remark that reports such paths as they get used.
Previous version of this patch tried to use the existing `LookupFileCache` to report used paths via `HitIdx`. That doesn't work for `ComputeUserEntryUsage` (which is intended to be called *after* preprocessing), because it indexes used search paths by the file name. This means the values get overwritten when the code contains `#include_next`.
Note that `HeaderSearch` doesn't use `HeaderSearchOptions::UserEntries` directly. Instead, `InitHeaderSearch` pre-processes them (adds platform-specific paths, removes duplicates, removes paths that don't exist) and creates `DirectoryLookup` instances. This means we need a mechanism for translating between those two. It's not possible to go from `DirectoryLookup` back to the original `HeaderSearch`, so `InitHeaderSearch` now tracks the relationships explicitly.
Depends on D111557.
Reviewed By: dexonsmith
Differential Revision: https://reviews.llvm.org/D102923
Diffstat (limited to 'lldb/test/API/lua_api/TestProcessAPI.lua')
0 files changed, 0 insertions, 0 deletions
