This patch adds support for Swift compiler producer strings to DWARFUnit.
Details
Diff Detail
Event Timeline
lldb/source/Plugins/SymbolFile/DWARF/DWARFUnit.cpp | ||
---|---|---|
685 | For consistency with the code below, should we first check if roducer.contains("swift") and then execute the regex? Otherwise the indentation on the line below is off. |
lldb/source/Plugins/SymbolFile/DWARF/DWARFUnit.cpp | ||
---|---|---|
674 | const? |
lldb/source/Plugins/SymbolFile/DWARF/DWARFUnit.cpp | ||
---|---|---|
685 | I think it makes more sense to run the clang regex right away. Matching the regex is faster than first searching for clang and then running the regex. |
lldb/source/Plugins/SymbolFile/DWARF/DWARFUnit.cpp | ||
---|---|---|
685 | No, that does not preserve the semantics. We want to set the producer even if we can't parse the version. In any case, scanning the string twice in the Swift case is unnecessary. |
LGTM
lldb/source/Plugins/SymbolFile/DWARF/DWARFUnit.cpp | ||
---|---|---|
685 | Sounds reasonable to me. Should we do the same for clang? Then we just need to fix the indentation on line 685. |
const?