forked from OSchip/llvm-project
fb244ffb9f
Current dsymutil implementation of hasLiveMemoryLocation()/hasLiveAddressRange() and applyValidRelocs() assume that calls should be done in certain order (from first Dies to last). Multi-thread implementation might call these methods in other order(it might process compilation units in order other than they are physically located), so we remove restriction that searching for relocations should be done in ascending order. This change does not introduce noticable performance degradation. The testing results for clang binary: golden-dsymutil/dsymutil 23787992 clang MD5: 5efa8fd9355ebf81b65f24db5375caa2 elapsed time=91sec build-Release/bin/dsymutil 23855616 clang MD5: 5efa8fd9355ebf81b65f24db5375caa2 elapsed time=91sec Differential Revision: https://reviews.llvm.org/D93106 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| DWARFLinker.cpp | ||
| DWARFLinkerCompileUnit.cpp | ||
| DWARFLinkerDeclContext.cpp | ||
| DWARFStreamer.cpp | ||