diff options
| author | Michal Rostecki <vadorovsky@protonmail.com> | 2024-09-20 15:34:42 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-20 14:34:42 +0100 |
| commit | c320df4a2c9d7be10caea9a423d2bfbdcaae6a39 (patch) | |
| tree | c9ac96b4210b9f3127ad622c1312ed5004223a10 /libcxx/src | |
| parent | 28646d0cc12a01b0de2e4eb982cb91590bc2f84a (diff) | |
| download | llvm-c320df4a2c9d7be10caea9a423d2bfbdcaae6a39.zip llvm-c320df4a2c9d7be10caea9a423d2bfbdcaae6a39.tar.gz llvm-c320df4a2c9d7be10caea9a423d2bfbdcaae6a39.tar.bz2 | |
[LLVM-C] Add bindings to `Instruction::getDbgRecordRange()` (#107802)
Since the migration from `@llvm.dbg.value` intrinsic to `#dbg_value`
records, there is no way to retrieve the debug records for an
`Instruction` in LLVM-C API.
Previously, with debug info intrinsics, retrieving debug info for an
`Instruction` could be done with `LLVMGetNextInstructions`, because the
intrinsic call was also an instruction.
However, to be able to retrieve debug info with the current LLVM, where
debug records are used, the `getDbgRecordRange()` iterator needs to be
exposed.
Add new functions for DbgRecord sequence traversal:
LLVMGetFirstDbgRecord
LLVMGetLastDbgRecord
LLVMGetNextDbgRecord
LLVMGetPreviousDbgRecord
See llvm/docs/RemoveDIsDebugInfo.md and release notes.
Diffstat (limited to 'libcxx/src')
0 files changed, 0 insertions, 0 deletions