Move DWARFImporterDelegate into ClangImporter and remove DWARFImporter.

This refactors DWARFImporter to become a part of ClangImporter, since
it needs access to many of its implementation details anyway. The
DWARFImporterDelegate is just another mechanism for deserializing
Clang ASTs and once we have a Clang AST, the processing is effectively
the same.
This commit is contained in:
Adrian Prantl
2019-08-13 17:12:00 -07:00
parent 5adac047b6
commit c08a62764a
24 changed files with 277 additions and 568 deletions

View File

@@ -220,10 +220,6 @@ int main(int argc, char **argv) {
desc("The directory that holds the compiler resource files"),
cat(Visible));
opt<bool> EnableDWARFImporter(
"enable-dwarf-importer",
desc("Import with LangOptions.EnableDWARFImporter = true"), cat(Visible));
ParseCommandLineOptions(argc, argv);
// Unregister our options so they don't interfere with the command line
@@ -290,7 +286,6 @@ int main(int argc, char **argv) {
Invocation.setModuleName("lldbtest");
Invocation.getClangImporterOptions().ModuleCachePath = ModuleCachePath;
Invocation.getLangOptions().EnableMemoryBufferImporter = true;
Invocation.getLangOptions().EnableDWARFImporter = EnableDWARFImporter;
if (!ResourceDir.empty()) {
Invocation.setRuntimeResourcePath(ResourceDir);