diff options
author | Jeremy Morse <jeremy.morse@sony.com> | 2023-11-15 15:55:34 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-11-15 15:55:34 +0000 |
commit | c2a2fd209e2da4c80e55d11b114d47b8d1eaaa16 (patch) | |
tree | f6b9964513387a5e6d2a57d1849449960818784f /llvm/tools/llvm-objdump/llvm-objdump.cpp | |
parent | de4139689519572b789b345ef1030d0f5aa5ac38 (diff) | |
download | llvm-c2a2fd209e2da4c80e55d11b114d47b8d1eaaa16.zip llvm-c2a2fd209e2da4c80e55d11b114d47b8d1eaaa16.tar.gz llvm-c2a2fd209e2da4c80e55d11b114d47b8d1eaaa16.tar.bz2 |
[DebugInfo][RemoveDIs] Allow for inserting DPValues at end() (#72379)
This trivial patch covers a bit of fallout from
https://reviews.llvm.org/D153990, where we moved the storage of trailing
DPValues into LLVMContext rather than being stored in each block. As a
result, you can now get a null DPMarker pointer from the end() iterator
where previously you didn't (and now it has to be explicitly created).
This is a sort-of stopgap measure -- there's another all-singing
all-dancing patch further down the line that refactors all of this so
that we don't allocate a DPMarker for every single Instruction. When
that lands this will all be refactored so that every time we request a
DPMarker, one is created if needs be. That's a performance-fix rather
than a functionality related patch though, so it'll come later.
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions