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/ELF/cfi-large-model.s

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

54 lines
2.0 KiB
ArmAsm
Raw Normal View History

Move `REQUIRES:` line to the top llvm-svn: 335635
2018-06-27 01:44:23 +08:00
// REQUIRES: powerpc-registered-target
// REQUIRES: x86-registered-target
Don't pass the code model to MC I was surprised to see the code model being passed to MC. After all, it assembles code, it doesn't create it. The one place it is used is in the expansion of .cfi directives to handle .eh_frame being more that 2gb away from the code. As far as I can tell, gnu assembler doesn't even have an option to enable this. Compiling a c file with gcc -mcmodel=large produces a regular looking .eh_frame. This is probably because in practice linker parse and recreate .eh_frames. In llvm this is used because the JIT can place the code and .eh_frame very far apart. Ideally we would fix the jit and delete this option. This is hard. Apart from confusion another problem with the current interface is that most callers pass CodeModel::Default, which is bad since MC has no way to map it to the target default if it actually needed to. This patch then replaces the argument with a boolean with a default value. The vast majority of users don't ever need to look at it. In fact, only CodeGen and llvm-mc use it and llvm-mc just to enable more testing. llvm-svn: 309884
2017-08-03 04:32:26 +08:00
// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu -large-code-model %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: -o - | llvm-readobj -S --sd | FileCheck --check-prefix=CHECK-X86 %s
Allow FDE references outside the +/-2GB range supported by PC relative offsets for code models other than small/medium. For JIT application, memory layout is less controlled and can result in truncations otherwise. Patch based on one by Olexa Bilaniuk! llvm-svn: 328400
2018-03-24 08:07:38 +08:00
// RUN: llvm-mc -filetype=obj -triple powerpc64le-linux-gnu -large-code-model %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: -o - | llvm-readobj -S --sd | FileCheck --check-prefix=CHECK-PPC %s
Commit back the correct bits of r222760 (was r222538). I also added a test. Original message: Allow FDE references outside the +/-2GB range supported by PC relative offsets for code models other than small/medium. For JIT application, memory layout is less controlled and can result in truncations otherwise. Patch from Akos Kiss. Differential Revision: http://reviews.llvm.org/D6079 llvm-svn: 222897
2014-11-28 01:13:56 +08:00
Add REQUIRES lines for the targets being checked in this test. llvm-svn: 328408
2018-03-24 10:56:58 +08:00
Allow FDE references outside the +/-2GB range supported by PC relative offsets for code models other than small/medium. For JIT application, memory layout is less controlled and can result in truncations otherwise. Patch based on one by Olexa Bilaniuk! llvm-svn: 328400
2018-03-24 08:07:38 +08:00
// CHECK-X86: Section {
// CHECK-X86: Index:
// CHECK-X86: Name: .eh_frame
// CHECK-X86-NEXT: Type: SHT_X86_64_UNWIND
// CHECK-X86-NEXT: Flags [
// CHECK-X86-NEXT: SHF_ALLOC
// CHECK-X86-NEXT: ]
// CHECK-X86-NEXT: Address: 0x0
// CHECK-X86-NEXT: Offset: 0x40
// CHECK-X86-NEXT: Size: 56
// CHECK-X86-NEXT: Link: 0
// CHECK-X86-NEXT: Info: 0
// CHECK-X86-NEXT: AddressAlignment: 8
// CHECK-X86-NEXT: EntrySize: 0
// CHECK-X86-NEXT: SectionData (
// CHECK-X86-NEXT: 0000: 14000000 00000000 017A5200 01781001 |.........zR..x..|
// CHECK-X86-NEXT: 0010: 1C0C0708 90010000 1C000000 1C000000 |................|
// CHECK-X86-NEXT: 0020: 00000000 00000000 00000000 00000000 |................|
// CHECK-X86-NEXT: 0030: 00000000 00000000 |........|
// CHECK-X86-NEXT: )
// CHECK-PPC: Section {
// CHECK-PPC: Index:
// CHECK-PPC: Name: .eh_frame
// CHECK-PPC-NEXT: Type: SHT_PROGBITS
// CHECK-PPC-NEXT: Flags [
// CHECK-PPC-NEXT: SHF_ALLOC
// CHECK-PPC-NEXT: ]
// CHECK-PPC-NEXT: Address: 0x0
// CHECK-PPC-NEXT: Offset: 0x40
// CHECK-PPC-NEXT: Size: 48
// CHECK-PPC-NEXT: Link: 0
// CHECK-PPC-NEXT: Info: 0
// CHECK-PPC-NEXT: AddressAlignment: 8
// CHECK-PPC-NEXT: EntrySize: 0
// CHECK-PPC-NEXT: SectionData (
// CHECK-PPC-NEXT: 0000: 10000000 00000000 017A5200 04784101 |.........zR..xA.|
// CHECK-PPC-NEXT: 0010: 1C0C0100 18000000 18000000 00000000 |................|
// CHECK-PPC-NEXT: 0020: 00000000 00000000 00000000 00000000 |................|
// CHECK-PPC-NEXT: )
// CHECK-PPC-NEXT: }
Commit back the correct bits of r222760 (was r222538). I also added a test. Original message: Allow FDE references outside the +/-2GB range supported by PC relative offsets for code models other than small/medium. For JIT application, memory layout is less controlled and can result in truncations otherwise. Patch from Akos Kiss. Differential Revision: http://reviews.llvm.org/D6079 llvm-svn: 222897
2014-11-28 01:13:56 +08:00
f:
.cfi_startproc
.cfi_endproc