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-directive-personalityind...

204 lines
4.0 KiB
ArmAsm
Raw Normal View History

ARM IAS: support .personalityindex The .personalityindex directive is equivalent to the .personality directive with the ARM EABI personality with the specific index (0, 1, 2). Both of these directives indicate personality routines, so enhance the personality directive handling to take into account personalityindex. Bonus fix: flush the UnwindContext at the beginning of a new function. Thanks to Logan Chien for additional tests! llvm-svn: 199706
2014-01-21 10:33:02 +08:00
@ RUN: llvm-mc -triple armv7-linux-eabi -filetype obj -o - %s \
[llvm-readobj] Change -long-option to --long-option in tests. NFC We use both -long-option and --long-option in tests. Switch to --long-option for consistency. In the "llvm-readelf" mode, -long-option is discouraged as it conflicts with grouped short options and it is not accepted by GNU readelf. While updating the tests, change llvm-readobj -s to llvm-readobj -S to reduce confusion ("s" is --section-headers in llvm-readobj but --symbols in llvm-readelf). llvm-svn: 359649
2019-05-01 13:27:20 +08:00
@ RUN: | llvm-readobj -S --sd --sr > %t
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: FileCheck %s < %t
@ RUN: FileCheck --check-prefix=RELOC %s < %t
ARM IAS: support .personalityindex The .personalityindex directive is equivalent to the .personality directive with the ARM EABI personality with the specific index (0, 1, 2). Both of these directives indicate personality routines, so enhance the personality directive handling to take into account personalityindex. Bonus fix: flush the UnwindContext at the beginning of a new function. Thanks to Logan Chien for additional tests! llvm-svn: 199706
2014-01-21 10:33:02 +08:00
.syntax unified
.thumb
.section .pr0
.global pr0
.type pr0,%function
.thumb_func
pr0:
.fnstart
.personalityindex 0
bx lr
.fnend
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.pr0
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 B0B0B080
@ CHECK: )
@ CHECK: }
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.pr0
@ 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 .pr0 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: }
ARM IAS: support .personalityindex The .personalityindex directive is equivalent to the .personality directive with the ARM EABI personality with the specific index (0, 1, 2). Both of these directives indicate personality routines, so enhance the personality directive handling to take into account personalityindex. Bonus fix: flush the UnwindContext at the beginning of a new function. Thanks to Logan Chien for additional tests! llvm-svn: 199706
2014-01-21 10:33:02 +08:00
.section .pr0.nontrivial
.global pr0_nontrivial
.type pr0_nontrivial,%function
.thumb_func
pr0_nontrivial:
.fnstart
.personalityindex 0
.pad #0x10
sub sp, sp, #0x10
add sp, sp, #0x10
bx lr
.fnend
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.pr0.nontrivial
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 B0B00380
@ CHECK: )
@ CHECK: }
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.pr0.nontrivial
@ 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 .pr0.nontrivial 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: }
ARM IAS: support .personalityindex The .personalityindex directive is equivalent to the .personality directive with the ARM EABI personality with the specific index (0, 1, 2). Both of these directives indicate personality routines, so enhance the personality directive handling to take into account personalityindex. Bonus fix: flush the UnwindContext at the beginning of a new function. Thanks to Logan Chien for additional tests! llvm-svn: 199706
2014-01-21 10:33:02 +08:00
.section .pr1
.global pr1
.type pr1,%function
.thumb_func
pr1:
.fnstart
.personalityindex 1
bx lr
.fnend
@ CHECK: Section {
@ CHECK: Name: .ARM.extab.pr1
@ CHECK: SectionData (
@ CHECK: 0000: B0B00081 00000000
@ CHECK: )
@ CHECK: }
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.pr1
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 00000000
@ CHECK: )
@ CHECK: }
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.pr1
@ RELOC: Relocations [
@ RELOC: 0x0 R_ARM_NONE __aeabi_unwind_cpp_pr1 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 .pr1 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: 0x4 R_ARM_PREL31 .ARM.extab.pr1 0x0
@ RELOC: ]
@ RELOC: }
ARM IAS: support .personalityindex The .personalityindex directive is equivalent to the .personality directive with the ARM EABI personality with the specific index (0, 1, 2). Both of these directives indicate personality routines, so enhance the personality directive handling to take into account personalityindex. Bonus fix: flush the UnwindContext at the beginning of a new function. Thanks to Logan Chien for additional tests! llvm-svn: 199706
2014-01-21 10:33:02 +08:00
.section .pr1.nontrivial
.global pr1_nontrivial
.type pr1_nontrivial,%function
.thumb_func
pr1_nontrivial:
.fnstart
.personalityindex 1
.pad #0x10
sub sp, sp, #0x10
add sp, sp, #0x10
bx lr
.fnend
@ CHECK: Section {
@ CHECK: Name: .ARM.extab.pr1.nontrivial
@ CHECK: SectionData (
@ CHECK: 0000: B0030081 00000000
@ CHECK: )
@ CHECK: }
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.pr1.nontrivial
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 00000000
@ CHECK: )
@ CHECK: }
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.pr1.nontrivial
@ RELOC: Relocations [
@ RELOC: 0x0 R_ARM_NONE __aeabi_unwind_cpp_pr1 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 .pr1.nontrivial 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: 0x4 R_ARM_PREL31 .ARM.extab.pr1.nontrivial 0x0
@ RELOC: ]
@ RELOC: }
ARM IAS: support .personalityindex The .personalityindex directive is equivalent to the .personality directive with the ARM EABI personality with the specific index (0, 1, 2). Both of these directives indicate personality routines, so enhance the personality directive handling to take into account personalityindex. Bonus fix: flush the UnwindContext at the beginning of a new function. Thanks to Logan Chien for additional tests! llvm-svn: 199706
2014-01-21 10:33:02 +08:00
.section .pr2
.global pr2
.type pr2,%function
.thumb_func
pr2:
.fnstart
.personalityindex 2
bx lr
.fnend
@ CHECK: Section {
@ CHECK: Name: .ARM.extab.pr2
@ CHECK: SectionData (
@ CHECK: 0000: B0B00082 00000000
@ CHECK: )
@ CHECK: }
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.pr2
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 00000000
@ CHECK: )
@ CHECK: }
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.pr2
@ RELOC: Relocations [
@ RELOC: 0x0 R_ARM_NONE __aeabi_unwind_cpp_pr2 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 .pr2 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: 0x4 R_ARM_PREL31 .ARM.extab.pr2 0x0
@ RELOC: ]
@ RELOC: }
ARM IAS: support .personalityindex The .personalityindex directive is equivalent to the .personality directive with the ARM EABI personality with the specific index (0, 1, 2). Both of these directives indicate personality routines, so enhance the personality directive handling to take into account personalityindex. Bonus fix: flush the UnwindContext at the beginning of a new function. Thanks to Logan Chien for additional tests! llvm-svn: 199706
2014-01-21 10:33:02 +08:00
.section .pr2.nontrivial
.type pr2_nontrivial,%function
.thumb_func
pr2_nontrivial:
.fnstart
.personalityindex 2
.pad #0x10
sub sp, sp, #0x10
add sp, sp, #0x10
bx lr
.fnend
@ CHECK: Section {
@ CHECK: Name: .ARM.extab.pr2.nontrivial
@ CHECK: SectionData (
@ CHECK: 0000: B0030082 00000000
@ CHECK: )
@ CHECK: }
@ CHECK: Section {
@ CHECK: Name: .ARM.exidx.pr2.nontrivial
@ CHECK: SectionData (
@ CHECK: 0000: 00000000 00000000
@ CHECK: )
@ CHECK: }
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.pr2.nontrivial
@ RELOC: Relocations [
@ RELOC: 0x0 R_ARM_NONE __aeabi_unwind_cpp_pr2 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 .pr2.nontrivial 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: 0x4 R_ARM_PREL31 .ARM.extab.pr2.nontrivial 0x0
@ RELOC: ]
@ RELOC: }