[PATCH] D88767: Show register names in DWARF unwind info.
Greg Clayton via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Tue Oct 6 16:38:41 PDT 2020
clayborg added a comment.
In D88767#2315279 <https://reviews.llvm.org/D88767#2315279>, @JamesNagurne wrote:
> In llvm/test/DebugInfo/dwarfdump-debug-frame-simple.test
>
> Our team maintains a downstream ARM target. The compiler, and indeed llvm-dwarfdump, are not built with the target used to build the object file queried here. Therefore, it does not know to use ESP or EIP and dumps reg4/reg8 instead.
> Has any other downstream compiler seen this? I'm not able to access the buildbots right at the moment.
>
> Specifically, here's the output from our lit test run with this change integrated into our downstream build:
>
> llvm/test/DebugInfo/Inputs/dwarfdump-test-32bit.elf.o: No available targets are compatible with triple "i386-unknown-unknown"
> llvm/test/DebugInfo/Inputs/dwarfdump-test-32bit.elf.o: file format elf32-i386
>
> .debug_frame contents:
>
> 00000000 00000010 ffffffff CIE
> Format: DWARF32
> Version: 1
> Augmentation: ""
> Code alignment factor: 1
> Data alignment factor: -4
> Return address column: 8
>
> DW_CFA_def_cfa: reg4 +4
> DW_CFA_offset: reg8 -4
> DW_CFA_nop:
> DW_CFA_nop:
>
> I suspect that if we really desire ESP/EIP, the test will need to be excluded when the i386 target is not available.
Or this could be switched to a regex that accepts "reg4" or "ESP" or "reg8" or "EIP"?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D88767/new/
https://reviews.llvm.org/D88767
More information about the llvm-commits
mailing list