maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MC/ARM/eh-compact-pr0.s

112 lines
3.7 KiB
ArmAsm
Raw Normal View History

Implement AsmParser for ARM unwind directives. This commit implements the AsmParser for fnstart, fnend, cantunwind, personality, handlerdata, pad, setfp, save, and vsave directives. This commit fixes some minor issue in the ARMELFStreamer: * The switch back to corresponding section after the .fnend directive. * Emit the unwind opcode while processing .fnend directive if there is no .handlerdata directive. * Emit the unwind opcode to .ARM.extab while processing .handlerdata even if .personality directive does not exist. llvm-svn: 181603
2013-05-11 00:17:24 +08:00
@ RUN: llvm-mc %s -triple=armv7-unknown-linux-gnueabi -filetype=obj -o - \
Don't depend on the order relocations are written to a .o file. llvm-svn: 235092
2015-04-16 20:59:30 +08:00
@ RUN: | llvm-readobj -s -sd -sr > %t
@ RUN: FileCheck %s < %t
@ RUN: FileCheck --check-prefix=RELOC %s < %t
Implement AsmParser for ARM unwind directives. This commit implements the AsmParser for fnstart, fnend, cantunwind, personality, handlerdata, pad, setfp, save, and vsave directives. This commit fixes some minor issue in the ARMELFStreamer: * The switch back to corresponding section after the .fnend directive. * Emit the unwind opcode while processing .fnend directive if there is no .handlerdata directive. * Emit the unwind opcode to .ARM.extab while processing .handlerdata even if .personality directive does not exist. llvm-svn: 181603
2013-05-11 00:17:24 +08:00
@ Check the compact pr0 model
.syntax unified
.section .TEST1
.globl func1
.align 2
.type func1,%function
func1:
.fnstart
.save {r11, lr}
push {r11, lr}
.setfp r11, sp
mov r11, sp
pop {r11, lr}
mov pc, lr
.fnend
.section .TEST2
.globl func2
.align 2
.type func2,%function
func2:
.fnstart
.save {r11, lr}
push {r11, lr}
pop {r11, pc}
.fnend
@-------------------------------------------------------------------------------
@ Check .TEST1 section
@-------------------------------------------------------------------------------
@ CHECK: Sections [
@ CHECK: Section {
@ CHECK: Name: .TEST1
@ CHECK: SectionData (
@ CHECK: 0000: 00482DE9 0DB0A0E1 0048BDE8 0EF0A0E1 |.H-......H......|
@ CHECK: )
@ CHECK: }
@-------------------------------------------------------------------------------
@ Check .ARM.exidx.TEST1 section
@-------------------------------------------------------------------------------
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.TEST1
@-------------------------------------------------------------------------------
@ 0x80 = Compact model 0, personality routine: __aeabi_unwind_cpp_pr0
@ 0x9B = $sp can be found in $r11
@ 0x8480 = pop {r11, r14}
@-------------------------------------------------------------------------------
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 80849B80 |........|
@ CHECK: )
@ CHECK: }
Change how we iterate over relocations on ELF. For COFF and MachO, sections semantically have relocations that apply to them. That is not the case on ELF. In relocatable objects (.o), a section with relocations in ELF has offsets to another section where the relocations should be applied. In dynamic objects and executables, relocations don't have an offset, they have a virtual address. The section sh_info may or may not point to another section, but that is not actually used for resolving the relocations. This patch exposes that in the ObjectFile API. It has the following advantages: * Most (all?) clients can handle this more efficiently. They will normally walk all relocations, so doing an effort to iterate in a particular order doesn't save time. * llvm-readobj now prints relocations in the same way the native readelf does. * probably most important, relocations that don't point to any section are now visible. This is the case of relocations in the rela.dyn section. See the updated relocation-executable.test for example. llvm-svn: 182908
2013-05-30 11:05:14 +08:00
@-------------------------------------------------------------------------------
@ The first word should be relocated to .TEST1 section. Besides, there is
@ another relocation entry for __aeabi_unwind_cpp_pr0, so that the linker
@ will keep __aeabi_unwind_cpp_pr0.
@-------------------------------------------------------------------------------
Don't depend on the order relocations are written to a .o file. llvm-svn: 235092
2015-04-16 20:59:30 +08:00
@ RELOC: Section {
@ RELOC: Name: .rel.ARM.exidx.TEST1
@ RELOC: Relocations [
@ RELOC: 0x0 R_ARM_NONE __aeabi_unwind_cpp_pr0 0x0
Avoid explicit relocation sorting most of the time. These days relocations are created and stored in a deterministic way. The order they are created is also suitable for the .o file, so we don't need an explicit sort. The last remaining exception is MIPS. llvm-svn: 255902
2015-12-18 00:22:06 +08:00
@ RELOC: 0x0 R_ARM_PREL31 .TEST1 0x0
Don't depend on the order relocations are written to a .o file. llvm-svn: 235092
2015-04-16 20:59:30 +08:00
@ RELOC: ]
@ RELOC: }
Implement AsmParser for ARM unwind directives. This commit implements the AsmParser for fnstart, fnend, cantunwind, personality, handlerdata, pad, setfp, save, and vsave directives. This commit fixes some minor issue in the ARMELFStreamer: * The switch back to corresponding section after the .fnend directive. * Emit the unwind opcode while processing .fnend directive if there is no .handlerdata directive. * Emit the unwind opcode to .ARM.extab while processing .handlerdata even if .personality directive does not exist. llvm-svn: 181603
2013-05-11 00:17:24 +08:00
@-------------------------------------------------------------------------------
@ Check .TEST2 section
@-------------------------------------------------------------------------------
@ CHECK: Section {
@ CHECK: Name: .TEST2
@ CHECK: SectionData (
@ CHECK: 0000: 00482DE9 0088BDE8 |.H-.....|
@ CHECK: )
@ CHECK: }
@-------------------------------------------------------------------------------
@ Check .ARM.exidx.TEST1 section
@-------------------------------------------------------------------------------
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.TEST2
@-------------------------------------------------------------------------------
@ 0x80 = Compact model 0, personality routine: __aeabi_unwind_cpp_pr0
@ 0x8480 = pop {r11, r14}
@ 0xB0 = finish
@-------------------------------------------------------------------------------
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 B0808480 |........|
@ CHECK: )
@ CHECK: }
Change how we iterate over relocations on ELF. For COFF and MachO, sections semantically have relocations that apply to them. That is not the case on ELF. In relocatable objects (.o), a section with relocations in ELF has offsets to another section where the relocations should be applied. In dynamic objects and executables, relocations don't have an offset, they have a virtual address. The section sh_info may or may not point to another section, but that is not actually used for resolving the relocations. This patch exposes that in the ObjectFile API. It has the following advantages: * Most (all?) clients can handle this more efficiently. They will normally walk all relocations, so doing an effort to iterate in a particular order doesn't save time. * llvm-readobj now prints relocations in the same way the native readelf does. * probably most important, relocations that don't point to any section are now visible. This is the case of relocations in the rela.dyn section. See the updated relocation-executable.test for example. llvm-svn: 182908
2013-05-30 11:05:14 +08:00
@-------------------------------------------------------------------------------
@ The first word should be relocated to .TEST2 section. Besides, there is
@ another relocation entry for __aeabi_unwind_cpp_pr0, so that the linker
@ will keep __aeabi_unwind_cpp_pr0.
@-------------------------------------------------------------------------------
Don't depend on the order relocations are written to a .o file. llvm-svn: 235092
2015-04-16 20:59:30 +08:00
@ RELOC: Section {
@ RELOC: Name: .rel.ARM.exidx.TEST2
@ RELOC: Relocations [
@ RELOC: 0x0 R_ARM_NONE __aeabi_unwind_cpp_pr0 0x0
Avoid explicit relocation sorting most of the time. These days relocations are created and stored in a deterministic way. The order they are created is also suitable for the .o file, so we don't need an explicit sort. The last remaining exception is MIPS. llvm-svn: 255902
2015-12-18 00:22:06 +08:00
@ RELOC: 0x0 R_ARM_PREL31 .TEST2 0x0
Don't depend on the order relocations are written to a .o file. llvm-svn: 235092
2015-04-16 20:59:30 +08:00
@ RELOC: ]
@ RELOC: }