llvm-project/llvm/test/tools/llvm-objdump/eh_frame_zero_cie.test

# RUN: llvm-objdump --dwarf=frames %p/Inputs/eh_frame_zero_cie.o 2>/dev/null | FileCheck %s

# CHECK:       .eh_frame contents:
# CHECK-EMPTY:
# CHECK-NEXT:  00000000 ZERO terminator
# CHECK-NOT:   {{.}}
[llvm-objdump][test] Change llvm-objdump tests to use double dash options 2020-03-16 06:30:18 +08:00			`# RUN: llvm-objdump --dwarf=frames %p/Inputs/eh_frame_zero_cie.o 2>/dev/null \| FileCheck %s`
[DebugInfo] Support zero-length CIE in the _eh_frame parser MCJIT emits zero-length CIE at the end of the _eh_frame section. This change ensures that parser inside DebugInfo will not crash and correctly record such cases. We are now recording DW_EH_PE_omit as a default value for FDE and LSDA encodings. Also Offset != EndAugmentationOffset assertion check will only happen if augmentation string had 'z' letter in it. Differential Revision: http://reviews.llvm.org/D16588 llvm-svn: 258931 2016-01-27 22:05:35 +08:00
[DebugInfo/llvm-objdump] - Print "ZERO terminator" for terminator entries when dumping .eh_frame. A CIE with the Length == 0 is a terminator: https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/ehframechpt.html And GNU objdump recognizes them and prints the following for such entries: "00000000 ZERO terminator" This patch teaches llvm-objdump to do the same. I had to update tests to use "CHECK-NEXT" too. (Note: it looks perhaps not right that printing is done inside the DebugInfo library, I'd expect to see the change in the llvm-objdump's code somewhere instead, but that is how it done atm). Differential revision: https://reviews.llvm.org/D80476 2020-05-23 23:34:08 +08:00			`# CHECK: .eh_frame contents:`
			`# CHECK-EMPTY:`
			`# CHECK-NEXT: 00000000 ZERO terminator`
			`# CHECK-NOT: {{.}}`