diff options
| author | Alex Langford <alangford@apple.com> | 2023-10-02 16:16:36 -0700 |
|---|---|---|
| committer | Alex Langford <alangford@apple.com> | 2023-10-03 10:27:18 -0700 |
| commit | dd76375c80098be4d08b7e02290e39a8c1d00ab1 (patch) | |
| tree | 72ddc4d8e417249b8ce89c8cba53017e9d20d6da /lldb/packages/Python/lldbsuite/test/lldbbench.py | |
| parent | 6f43d28f3452b3ef598bc12b761cfc2dbd0f34c9 (diff) | |
| download | llvm-dd76375c80098be4d08b7e02290e39a8c1d00ab1.zip llvm-dd76375c80098be4d08b7e02290e39a8c1d00ab1.tar.gz llvm-dd76375c80098be4d08b7e02290e39a8c1d00ab1.tar.bz2 | |
[lldb][NFCI] Apply IndexEntry to DWARFUnitHeader outside of extraction
I plan on replacing LLDB's DWARFUnitHeader implementation with LLVM's.
LLVM's DWARFUnitHeader::extract applies the DWARFUnitIndex::Entry to a
given DWARFUnitHeader outside of the extraction because the index entry
is only relevant to one place where we may parse DWARFUnitHeaders
(specifically when we're creating a DWARFUnit in a DWO context). To ease
the transition, I've reshaped LLDB's implementation to look closer to
LLVM's.
Reviewed By: aprantl, fdeazeve
Differential Revision: https://reviews.llvm.org/D151919
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbbench.py')
0 files changed, 0 insertions, 0 deletions