diff options
author | Momchil Velikov <momchil.velikov@arm.com> | 2022-03-24 15:27:04 +0000 |
---|---|---|
committer | Momchil Velikov <momchil.velikov@arm.com> | 2022-03-24 16:16:44 +0000 |
commit | 50a97aacacf689f838451439d913421d608e1bed (patch) | |
tree | 591c0459585508f74e9182790901e37e96db0c13 /clang/lib/ExtractAPI/Serialization/SymbolGraphSerializer.cpp | |
parent | 44b0ea44f26d405f663d20b067dafd514cb5b26a (diff) | |
download | llvm-50a97aacacf689f838451439d913421d608e1bed.zip llvm-50a97aacacf689f838451439d913421d608e1bed.tar.gz llvm-50a97aacacf689f838451439d913421d608e1bed.tar.bz2 |
[AArch64] Async unwind - function prologues
Re-commit of 32e8b550e5439c7e4aafa73894faffd5f25d0d05
This patch rearranges emission of CFI instructions, so the resulting
DWARF and `.eh_frame` information is precise at every instruction.
The current state is that the unwind info is emitted only after the
function prologue. This is fine for synchronous (e.g. C++) exceptions,
but the information is generally incorrect when the program counter is
at an instruction in the prologue or the epilogue, for example:
```
stp x29, x30, [sp, #-16]! // 16-byte Folded Spill
mov x29, sp
.cfi_def_cfa w29, 16
...
```
after the `stp` is executed the (initial) rule for the CFA still says
the CFA is in the `sp`, even though it's already offset by 16 bytes
A correct unwind info could look like:
```
stp x29, x30, [sp, #-16]! // 16-byte Folded Spill
.cfi_def_cfa_offset 16
mov x29, sp
.cfi_def_cfa w29, 16
...
```
Having this information precise up to an instruction is useful for
sampling profilers that would like to get a stack backtrace. The end
goal (towards this patch is just a step) is to have fully working
`-fasynchronous-unwind-tables`.
Reviewed By: danielkiss, MaskRay
Differential Revision: https://reviews.llvm.org/D111411
Diffstat (limited to 'clang/lib/ExtractAPI/Serialization/SymbolGraphSerializer.cpp')
0 files changed, 0 insertions, 0 deletions