aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/LockFileManager.cpp
diff options
context:
space:
mode:
authorAlexey Samsonov <vonosmas@gmail.com>2014-06-12 23:58:49 +0000
committerAlexey Samsonov <vonosmas@gmail.com>2014-06-12 23:58:49 +0000
commit0670cfaf01bc70c159132836be62c8b91e18dedb (patch)
treea2ca45ce8c200ae8c09ec91690aff769e9f74ca9 /llvm/lib/Support/LockFileManager.cpp
parent70e005a1719978a134b0d65a38828b41338263fb (diff)
downloadllvm-0670cfaf01bc70c159132836be62c8b91e18dedb.zip
llvm-0670cfaf01bc70c159132836be62c8b91e18dedb.tar.gz
llvm-0670cfaf01bc70c159132836be62c8b91e18dedb.tar.bz2
[DWARF parser] Fix broken address ranges construction.
Previous algorithm for constructing [Address ranges]->[Compile Units] mapping was wrong. It somewhat relied on the assumption that address ranges for different compile units may not overlap. It is not so. For example, two compile units may contain the definition of the same linkonce_odr function. These definitions will be merged at link-time, resulting in equivalent .debug_ranges entries for both these units Instead of sorting and merging original address ranges (from .debug_ranges and .debug_aranges), implement a different approach: save endpoints of all ranges, and then use a sweep-line approach to construct the desired mapping. If we find that certain address maps to several compilation units, we just pick any of them. llvm-svn: 210860
Diffstat (limited to 'llvm/lib/Support/LockFileManager.cpp')
0 files changed, 0 insertions, 0 deletions