maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/ELF/emulation.s

209 lines
7.7 KiB
ArmAsm
Raw Normal View History

[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-mc -filetype=obj -triple=x86_64-unknown-linux %s -o %tx64
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld -m elf_x86_64 %tx64 -o %t2x64
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-readobj -file-headers %t2x64 | FileCheck --check-prefix=X86-64 %s
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld %tx64 -o %t3x64
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-readobj -file-headers %t3x64 | FileCheck --check-prefix=X86-64 %s
# X86-64: ElfHeader {
# X86-64-NEXT: Ident {
# X86-64-NEXT: Magic: (7F 45 4C 46)
# X86-64-NEXT: Class: 64-bit (0x2)
# X86-64-NEXT: DataEncoding: LittleEndian (0x1)
# X86-64-NEXT: FileVersion: 1
# X86-64-NEXT: OS/ABI: SystemV (0x0)
# X86-64-NEXT: ABIVersion: 0
# X86-64-NEXT: Unused: (00 00 00 00 00 00 00)
# X86-64-NEXT: }
# X86-64-NEXT: Type: Executable (0x2)
# X86-64-NEXT: Machine: EM_X86_64 (0x3E)
# X86-64-NEXT: Version: 1
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# X86-64-NEXT: Entry:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-64-NEXT: ProgramHeaderOffset: 0x40
Avoid checking for irrelevant facts. If the test is not for layout, it should not depend on the address for example. llvm-svn: 251969
2015-11-04 03:56:47 +08:00
# X86-64-NEXT: SectionHeaderOffset:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-64-NEXT: Flags [ (0x0)
# X86-64-NEXT: ]
# X86-64-NEXT: HeaderSize: 64
# X86-64-NEXT: ProgramHeaderEntrySize: 56
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# X86-64-NEXT: ProgramHeaderCount:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-64-NEXT: SectionHeaderEntrySize: 64
Avoid checking for irrelevant facts. If the test is not for layout, it should not depend on the address for example. llvm-svn: 251969
2015-11-04 03:56:47 +08:00
# X86-64-NEXT: SectionHeaderCount:
# X86-64-NEXT: StringTableSectionIndex:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-64-NEXT: }
# RUN: llvm-mc -filetype=obj -triple=i686-unknown-linux %s -o %tx86
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld -m elf_i386 %tx86 -o %t2x86
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-readobj -file-headers %t2x86 | FileCheck --check-prefix=X86 %s
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld %tx86 -o %t3x86
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-readobj -file-headers %t3x86 | FileCheck --check-prefix=X86 %s
# X86: ElfHeader {
# X86-NEXT: Ident {
# X86-NEXT: Magic: (7F 45 4C 46)
# X86-NEXT: Class: 32-bit (0x1)
# X86-NEXT: DataEncoding: LittleEndian (0x1)
# X86-NEXT: FileVersion: 1
# X86-NEXT: OS/ABI: SystemV (0x0)
# X86-NEXT: ABIVersion: 0
# X86-NEXT: Unused: (00 00 00 00 00 00 00)
# X86-NEXT: }
# X86-NEXT: Type: Executable (0x2)
# X86-NEXT: Machine: EM_386 (0x3)
# X86-NEXT: Version: 1
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# X86-NEXT: Entry:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-NEXT: ProgramHeaderOffset: 0x34
Avoid checking for irrelevant facts. If the test is not for layout, it should not depend on the address for example. llvm-svn: 251969
2015-11-04 03:56:47 +08:00
# X86-NEXT: SectionHeaderOffset:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-NEXT: Flags [ (0x0)
# X86-NEXT: ]
# X86-NEXT: HeaderSize: 52
# X86-NEXT: ProgramHeaderEntrySize: 32
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# X86-NEXT: ProgramHeaderCount:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-NEXT: SectionHeaderEntrySize: 40
Avoid checking for irrelevant facts. If the test is not for layout, it should not depend on the address for example. llvm-svn: 251969
2015-11-04 03:56:47 +08:00
# X86-NEXT: SectionHeaderCount:
# X86-NEXT: StringTableSectionIndex:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# X86-NEXT: }
lld: accept and ignore _fbsd suffix in emulation name Differential Revision: http://reviews.llvm.org/D18661 llvm-svn: 265044
2016-04-01 04:26:30 +08:00
# RUN: llvm-mc -filetype=obj -triple=i686-unknown-freebsd %s -o %tx86fbsd
# RUN: ld.lld -m elf_i386_fbsd %tx86fbsd -o %t2x86_fbsd
# RUN: llvm-readobj -file-headers %t2x86_fbsd | FileCheck --check-prefix=X86FBSD %s
# RUN: ld.lld %tx86fbsd -o %t3x86fbsd
# RUN: llvm-readobj -file-headers %t3x86fbsd | FileCheck --check-prefix=X86FBSD %s
# X86FBSD: ElfHeader {
# X86FBSD-NEXT: Ident {
# X86FBSD-NEXT: Magic: (7F 45 4C 46)
# X86FBSD-NEXT: Class: 32-bit (0x1)
# X86FBSD-NEXT: DataEncoding: LittleEndian (0x1)
# X86FBSD-NEXT: FileVersion: 1
# X86FBSD-NEXT: OS/ABI: FreeBSD (0x9)
# X86FBSD-NEXT: ABIVersion: 0
# X86FBSD-NEXT: Unused: (00 00 00 00 00 00 00)
# X86FBSD-NEXT: }
# X86FBSD-NEXT: Type: Executable (0x2)
# X86FBSD-NEXT: Machine: EM_386 (0x3)
# X86FBSD-NEXT: Version: 1
# X86FBSD-NEXT: Entry:
# X86FBSD-NEXT: ProgramHeaderOffset: 0x34
# X86FBSD-NEXT: SectionHeaderOffset:
# X86FBSD-NEXT: Flags [ (0x0)
# X86FBSD-NEXT: ]
# X86FBSD-NEXT: HeaderSize: 52
# X86FBSD-NEXT: ProgramHeaderEntrySize: 32
# X86FBSD-NEXT: ProgramHeaderCount:
# X86FBSD-NEXT: SectionHeaderEntrySize: 40
# X86FBSD-NEXT: SectionHeaderCount:
# X86FBSD-NEXT: StringTableSectionIndex:
# X86FBSD-NEXT: }
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-mc -filetype=obj -triple=powerpc64-unknown-linux %s -o %tppc64
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld -m elf64ppc %tppc64 -o %t2ppc64
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-readobj -file-headers %t2ppc64 | FileCheck --check-prefix=PPC64 %s
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld %tppc64 -o %t3ppc64
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# RUN: llvm-readobj -file-headers %t3ppc64 | FileCheck --check-prefix=PPC64 %s
# PPC64: ElfHeader {
# PPC64-NEXT: Ident {
# PPC64-NEXT: Magic: (7F 45 4C 46)
# PPC64-NEXT: Class: 64-bit (0x2)
# PPC64-NEXT: DataEncoding: BigEndian (0x2)
# PPC64-NEXT: FileVersion: 1
# PPC64-NEXT: OS/ABI: SystemV (0x0)
# PPC64-NEXT: ABIVersion: 0
# PPC64-NEXT: Unused: (00 00 00 00 00 00 00)
# PPC64-NEXT: }
# PPC64-NEXT: Type: Executable (0x2)
# PPC64-NEXT: Machine: EM_PPC64 (0x15)
# PPC64-NEXT: Version: 1
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# PPC64-NEXT: Entry:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# PPC64-NEXT: ProgramHeaderOffset: 0x40
Avoid checking for irrelevant facts. If the test is not for layout, it should not depend on the address for example. llvm-svn: 251969
2015-11-04 03:56:47 +08:00
# PPC64-NEXT: SectionHeaderOffset:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# PPC64-NEXT: Flags [ (0x0)
# PPC64-NEXT: ]
# PPC64-NEXT: HeaderSize: 64
# PPC64-NEXT: ProgramHeaderEntrySize: 56
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# PPC64-NEXT: ProgramHeaderCount:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# PPC64-NEXT: SectionHeaderEntrySize: 64
Avoid checking for irrelevant facts. If the test is not for layout, it should not depend on the address for example. llvm-svn: 251969
2015-11-04 03:56:47 +08:00
# PPC64-NEXT: SectionHeaderCount:
# PPC64-NEXT: StringTableSectionIndex:
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
# PPC64-NEXT: }
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# RUN: llvm-mc -filetype=obj -triple=mips-unknown-linux %s -o %tmips
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld -m elf32btsmip -e _start %tmips -o %t2mips
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# RUN: llvm-readobj -file-headers %t2mips | FileCheck --check-prefix=MIPS %s
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld %tmips -e _start -o %t3mips
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# RUN: llvm-readobj -file-headers %t3mips | FileCheck --check-prefix=MIPS %s
# MIPS: ElfHeader {
# MIPS-NEXT: Ident {
# MIPS-NEXT: Magic: (7F 45 4C 46)
# MIPS-NEXT: Class: 32-bit (0x1)
# MIPS-NEXT: DataEncoding: BigEndian (0x2)
# MIPS-NEXT: FileVersion: 1
# MIPS-NEXT: OS/ABI: SystemV (0x0)
# MIPS-NEXT: ABIVersion: 0
# MIPS-NEXT: Unused: (00 00 00 00 00 00 00)
# MIPS-NEXT: }
# MIPS-NEXT: Type: Executable (0x2)
# MIPS-NEXT: Machine: EM_MIPS (0x8)
# MIPS-NEXT: Version: 1
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# MIPS-NEXT: Entry:
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# MIPS-NEXT: ProgramHeaderOffset: 0x34
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# MIPS-NEXT: SectionHeaderOffset:
[ELF] Allow target to configure ELF header flags in the output file The patch configure ELF header flags for MIPS target. For now the flags are hard coded. In fact they depends on ELF flags of input object files and selected emulation. Differential Revision: http://reviews.llvm.org/D15575 llvm-svn: 256089
2015-12-19 13:51:49 +08:00
# MIPS-NEXT: Flags [
# MIPS-NEXT: EF_MIPS_ABI_O32
# MIPS-NEXT: EF_MIPS_ARCH_32R2
# MIPS-NEXT: EF_MIPS_CPIC
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# MIPS-NEXT: ]
# RUN: llvm-mc -filetype=obj -triple=mipsel-unknown-linux %s -o %tmipsel
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld -m elf32ltsmip -e _start %tmipsel -o %t2mipsel
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# RUN: llvm-readobj -file-headers %t2mipsel | FileCheck --check-prefix=MIPSEL %s
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld -melf32ltsmip -e _start %tmipsel -o %t2mipsel
[Driver] Accept both -m <emulation> and -m<emulation> GNU linkers accept both variants and at least for MIPS target gcc passes joined variant of the '-m' option. Differential Revision: http://reviews.llvm.org/D14133 llvm-svn: 251497
2015-10-28 13:13:12 +08:00
# RUN: llvm-readobj -file-headers %t2mipsel | FileCheck --check-prefix=MIPSEL %s
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
# RUN: ld.lld %tmipsel -e _start -o %t3mipsel
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# RUN: llvm-readobj -file-headers %t3mipsel | FileCheck --check-prefix=MIPSEL %s
# MIPSEL: ElfHeader {
# MIPSEL-NEXT: Ident {
# MIPSEL-NEXT: Magic: (7F 45 4C 46)
# MIPSEL-NEXT: Class: 32-bit (0x1)
# MIPSEL-NEXT: DataEncoding: LittleEndian (0x1)
# MIPSEL-NEXT: FileVersion: 1
# MIPSEL-NEXT: OS/ABI: SystemV (0x0)
# MIPSEL-NEXT: ABIVersion: 0
# MIPSEL-NEXT: Unused: (00 00 00 00 00 00 00)
# MIPSEL-NEXT: }
# MIPSEL-NEXT: Type: Executable (0x2)
# MIPSEL-NEXT: Machine: EM_MIPS (0x8)
# MIPSEL-NEXT: Version: 1
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# MIPSEL-NEXT: Entry:
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# MIPSEL-NEXT: ProgramHeaderOffset: 0x34
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
# MIPSEL-NEXT: SectionHeaderOffset:
[ELF] Allow target to configure ELF header flags in the output file The patch configure ELF header flags for MIPS target. For now the flags are hard coded. In fact they depends on ELF flags of input object files and selected emulation. Differential Revision: http://reviews.llvm.org/D15575 llvm-svn: 256089
2015-12-19 13:51:49 +08:00
# MIPSEL-NEXT: Flags [
# MIPSEL-NEXT: EF_MIPS_ABI_O32
# MIPSEL-NEXT: EF_MIPS_ARCH_32R2
# MIPSEL-NEXT: EF_MIPS_CPIC
[ELF2][mips] Support elf32ltsmip/elf32btsmip target emulation as the -m arguments llvm-svn: 249683
2015-10-08 20:13:38 +08:00
# MIPSEL-NEXT: ]
[ELF/AArch64] Accept -m aarch64linux. This option is passed by clang driver if the target triple is "aarch64-unknown-linux". Differential Revision: http://reviews.llvm.org/D14831 llvm-svn: 253639
2015-11-20 10:48:53 +08:00
# RUN: llvm-mc -filetype=obj -triple=aarch64-unknown-linux %s -o %taarch64
# RUN: ld.lld -m aarch64linux %taarch64 -o %t2aarch64
# RUN: llvm-readobj -file-headers %t2aarch64 | FileCheck --check-prefix=AARCH64 %s
# RUN: ld.lld %taarch64 -o %t3aarch64
# RUN: llvm-readobj -file-headers %t3aarch64 | FileCheck --check-prefix=AARCH64 %s
# AARCH64: ElfHeader {
# AARCH64-NEXT: Ident {
# AARCH64-NEXT: Magic: (7F 45 4C 46)
# AARCH64-NEXT: Class: 64-bit (0x2)
# AARCH64-NEXT: DataEncoding: LittleEndian (0x1)
# AARCH64-NEXT: FileVersion: 1
# AARCH64-NEXT: OS/ABI: SystemV (0x0)
# AARCH64-NEXT: ABIVersion: 0
# AARCH64-NEXT: Unused: (00 00 00 00 00 00 00)
# AARCH64-NEXT: }
# AARCH64-NEXT: Type: Executable (0x2)
# AARCH64-NEXT: Machine: EM_AARCH64 (0xB7)
# AARCH64-NEXT: Version: 1
# AARCH64-NEXT: Entry:
# AARCH64-NEXT: ProgramHeaderOffset: 0x40
# AARCH64-NEXT: SectionHeaderOffset:
# AARCH64-NEXT: Flags [ (0x0)
# AARCH64-NEXT: ]
# REQUIRES: x86,ppc,mips,aarch64
[ELF2] Handle -m option Parse and apply emulation given with -m option. Check input files to match ELF type and machine architecture provided with -m. Differential Revision: http://reviews.llvm.org/D13055 llvm-svn: 249529
2015-10-07 17:13:03 +08:00
.globl _start;
_start: