diff options
| author | Reid Kleckner <rnk@google.com> | 2019-05-31 20:55:31 +0000 |
|---|---|---|
| committer | Reid Kleckner <rnk@google.com> | 2019-05-31 20:55:31 +0000 |
| commit | e98cf5fe47f2585363588d7cdd19c5bfe57f2c13 (patch) | |
| tree | 8144f68a9ffe0401481cbe0b5c6258fa41edf422 /llvm/unittests/Analysis/TargetLibraryInfoTest.cpp | |
| parent | 7bafae55c01dda8478aeff74a8d657a4148630af (diff) | |
| download | llvm-e98cf5fe47f2585363588d7cdd19c5bfe57f2c13.zip llvm-e98cf5fe47f2585363588d7cdd19c5bfe57f2c13.tar.gz llvm-e98cf5fe47f2585363588d7cdd19c5bfe57f2c13.tar.bz2 | |
[codeview] Fix inline line table accuracy for discontiguous segments
After improving the inline line table dumper in llvm-pdbutil and looking
at MSVC's inline line tables, it is clear that setting the length of the
inlined code region does not update the code offset. This means that the
delta to the beginning of a new discontiguous inlined code region should
be calculated relative to the last code offset, excluding the length.
Implementing this is a one line fix for MC: simply don't update
LastLabel.
While I'm updating these test cases, switch them to use llvm-objdump -d
and llvm-pdbutil. This allows us to show offsets of each instruction and
correlate the line table offsets to the actual code.
llvm-svn: 362264
Diffstat (limited to 'llvm/unittests/Analysis/TargetLibraryInfoTest.cpp')
0 files changed, 0 insertions, 0 deletions