Class ExpansionContext encapsulates options for search and expansion of
response files, including configuration files. With this change the
directories which are searched for configuration files are also stored
in ExpansionContext.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang/lib/Driver/Driver.cpp | ||
---|---|---|
1020 | I don't really understand the purpose of this change, or how it's related to moving search dirs. |
clang/lib/Driver/Driver.cpp | ||
---|---|---|
1020 | Oh, it's because of ExpCtx.findConfigFile() API. |
llvm/include/llvm/Support/CommandLine.h | ||
---|---|---|
2197 | I'm sorry if I'm missing something obvious but is there a specific reason you're using std::string here when pretty much all prior call sites were using SmallString? |
llvm/include/llvm/Support/CommandLine.h | ||
---|---|---|
2197 | Changed type of this parameter to base of SmallString. |
I am not familiar with ExpansionContext. Is there any behavior difference which can be demonstrated by a test?
This is an NFC test, it does not change behavior. However moving these properties into ExpansionContext provides access to the search directories in the functions expandResponseFile(s) and allows more natural implementation of the functionality of D133325.
I don't really understand the purpose of this change, or how it's related to moving search dirs.