maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/mach-o/write-final-sections.yaml

147 lines
4.2 KiB
YAML
Raw Normal View History

Delete unnecessary generality in loadFile. loadFile could load mulitple files just because yaml has a feature for putting multiple documents in one file. Designing a linker around what yaml can do seems like a bad idea to me. This patch changes it to read a single file. There are further improvements to be done to the api and they will follow shortly. llvm-svn: 235724
2015-04-24 23:51:45 +08:00
# RUN: lld -flavor darwin -arch x86_64 %s %p/Inputs/write-final-sections.yaml \
# RUN: -o %t -e _foo
MachO: re-enable writing of compact-unwind sections. This isn't really the right place to put them in final object files (that would be __TEXT,__unwind_info), but the format is different between relocatable and final objects, which means we really need a pass to handle the translation. For now, re-emitting in __LD,__compact_unwind is harmless (dyld ignores it and moves straight on to inspecting __TEXT,__eh_frame), and sidesteps an assertion failure when processing files containing compact-unwind info. llvm-svn: 212032
2014-06-30 17:49:37 +08:00
# RUN: llvm-readobj -sections -section-data %t | FileCheck %s
--- !native
defined-atoms:
# For __TEXT, __text (with typeCode)
- name: _foo
scope: global
content: [ 55 ]
# CHECK: Name: __text
# CHECK: Segment: __TEXT
# CHECK: SectionData (
MachO: stop iterating past the end of an array When trying to map atom types to sections, we were iterating through an array until we hit a sentinel value. There's no need for such dances when range-based for loops are available. llvm-svn: 212035
2014-06-30 18:30:00 +08:00
# CHECK-NEXT: 0000: 55
MachO: re-enable writing of compact-unwind sections. This isn't really the right place to put them in final object files (that would be __TEXT,__unwind_info), but the format is different between relocatable and final objects, which means we really need a pass to handle the translation. For now, re-emitting in __LD,__compact_unwind is harmless (dyld ignores it and moves straight on to inspecting __TEXT,__eh_frame), and sidesteps an assertion failure when processing files containing compact-unwind info. llvm-svn: 212032
2014-06-30 17:49:37 +08:00
# CHECK-NEXT: )
# For __TEXT, __const (with typeConstant),
- type: constant
content: [ 01, 00, 00, 00 ]
# From __TEXT, __literal4, (with typeLiteral4)
- scope: hidden
type: const-4-byte
content: [ 02, 00, 00, 00 ]
# From __TEXT, __literal8, (with typeLiteral8)
- scope: hidden
type: const-8-byte
content: [ 03, 00, 00, 00, 00, 00, 00, 00 ]
# From __TEXT, __literal16, (with typeLiteral16)
- scope: hidden
type: const-16-byte
content: [ 04, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00 ]
# CHECK: Name: __const
# CHECK: Segment: __TEXT
# CHECK: SectionData (
# CHECK-NEXT: 0000: 01000000 02000000 03000000 00000000
# CHECK-NEXT: 0010: 04000000 00000000 00000000 00000000
# CHECK-NEXT: )
# For __TEXT, __cstring (with typeCString)
- scope: hidden
type: c-string
content: [ 57, 69, 62, 62, 6C, 65, 00 ]
merge: by-content
# CHECK: Name: __cstring
# CHECK: Segment: __TEXT
# CHECK: SectionData (
# CHECK-NEXT: 0000: 57696262 6C6500
# CHECK-NEXT: )
# For __TEXT, __ustring (with typeUTF16String)
- scope: hidden
type: utf16-string
content: [ 05, 00 ]
merge: by-content
# CHECK: Name: __ustring
# CHECK: Segment: __TEXT
# CHECK: SectionData (
# CHECK-NEXT: 0000: 0500
# CHECK-NEXT: )
# For __TEXT, __gcc_except_tab, (with typeLSDA)
- name: GCC_except_table0
type: unwind-lsda
content: [ 06, 00 ]
# CHECK: Name: __gcc_except_tab
# CHECK: Segment: __TEXT
# CHECK: SectionData (
# CHECK-NEXT: 0000: 0600
# CHECK-NEXT: )
# For __TEXT, __eh_frame, (with typeCFI)
- type: unwind-cfi
content: [ 07 ]
# CHECK: Name: __eh_frame
# CHECK: Segment: __TEXT
# CHECK: SectionData (
# CHECK-NEXT: 0000: 07
# CHECK-NEXT: )
# For __DATA, __data, (with typeData)
- name: var
type: data
content: [ 08 ]
# CHECK: Name: __data
# CHECK: Segment: __DATA
# CHECK: SectionData (
# CHECK-NEXT: 0000: 08
# CHECK-NEXT: )
[mach-o] remove extra leading underscore on __bss and __got llvm-svn: 221425
2014-11-06 09:14:12 +08:00
# For __DATA, __bss (with typeZeroFill)
MachO: re-enable writing of compact-unwind sections. This isn't really the right place to put them in final object files (that would be __TEXT,__unwind_info), but the format is different between relocatable and final objects, which means we really need a pass to handle the translation. For now, re-emitting in __LD,__compact_unwind is harmless (dyld ignores it and moves straight on to inspecting __TEXT,__eh_frame), and sidesteps an assertion failure when processing files containing compact-unwind info. llvm-svn: 212032
2014-06-30 17:49:37 +08:00
# FIXME: Attributes & tags of __bss are mostly broken. Should be at end of
# __DATA, should have size, should have S_ZEROFILL flag.
- type: zero-fill
size: 8
[mach-o] remove extra leading underscore on __bss and __got llvm-svn: 221425
2014-11-06 09:14:12 +08:00
# CHECK: Name: __bss
MachO: re-enable writing of compact-unwind sections. This isn't really the right place to put them in final object files (that would be __TEXT,__unwind_info), but the format is different between relocatable and final objects, which means we really need a pass to handle the translation. For now, re-emitting in __LD,__compact_unwind is harmless (dyld ignores it and moves straight on to inspecting __TEXT,__eh_frame), and sidesteps an assertion failure when processing files containing compact-unwind info. llvm-svn: 212032
2014-06-30 17:49:37 +08:00
# CHECK: Segment: __DATA
# For __DATA, __const, (with typeConstData)
- type: const-data
content: [ 09, 00, 00, 00 ]
# CHECK: Name: __const
# CHECK: Segment: __DATA
# CHECK: SectionData (
# CHECK-NEXT: 0000: 09000000
# CHECK-NEXT: )
# For __DATA, __cfstring, (with typeCFString)
- type: cfstring
content: [ 0A, 00 ]
# CHECK: Name: __cfstring
# CHECK: Segment: __DATA
# CHECK: SectionData (
# CHECK-NEXT: 0000: 0A00
# CHECK-NEXT: )
[mach-o] remove extra leading underscore on __bss and __got llvm-svn: 221425
2014-11-06 09:14:12 +08:00
# For __DATA, __got (with typeGOT)
MachO: re-enable writing of compact-unwind sections. This isn't really the right place to put them in final object files (that would be __TEXT,__unwind_info), but the format is different between relocatable and final objects, which means we really need a pass to handle the translation. For now, re-emitting in __LD,__compact_unwind is harmless (dyld ignores it and moves straight on to inspecting __TEXT,__eh_frame), and sidesteps an assertion failure when processing files containing compact-unwind info. llvm-svn: 212032
2014-06-30 17:49:37 +08:00
- type: got
content: [ 0B, 00, 00, 00, 00, 00, 00, 00 ]
[mach-o] remove extra leading underscore on __bss and __got llvm-svn: 221425
2014-11-06 09:14:12 +08:00
# CHECK: Name: __got
MachO: re-enable writing of compact-unwind sections. This isn't really the right place to put them in final object files (that would be __TEXT,__unwind_info), but the format is different between relocatable and final objects, which means we really need a pass to handle the translation. For now, re-emitting in __LD,__compact_unwind is harmless (dyld ignores it and moves straight on to inspecting __TEXT,__eh_frame), and sidesteps an assertion failure when processing files containing compact-unwind info. llvm-svn: 212032
2014-06-30 17:49:37 +08:00
# CHECK: Segment: __DATA
# CHECK: SectionData (
# CHECK-NEXT: 0000: 0B000000 00000000
# CHECK-NEXT: )
# For __DATA, __mod_init_func (with typeInitializerPtr)
- type: initializer-pointer
content: [ 0C, 00, 00, 00, 00, 00, 00, 00 ]
# CHECK: Name: __mod_init_func
# CHECK: Segment: __DATA
# CHECK: SectionData (
# CHECK-NEXT: 0000: 0C000000 00000000
# CHECK-NEXT: )
# For __DATA, __mod_term_func (with typeTerminatorPointer)
- type: terminator-pointer
content: [ 0D, 00, 00, 00, 00, 00, 00, 00 ]
# CHECK: Name: __mod_term_func
# CHECK: Segment: __DATA
# CHECK: SectionData (
# CHECK-NEXT: 0000: 0D000000 00000000
# CHECK-NEXT: )
- type: compact-unwind
content: [ 0E, 00, 00, 00, 00, 00, 00, 00 ]
[mach-o] remove __compact_unwind atoms once __unwind_info has been generated The job of the CompactUnwind pass is to turn __compact_unwind data (and __eh_frame) into the compressed final form in __unwind_info. After it's done, the original atoms are no longer relevant and should be deleted (they cause problems during actual execution, quite apart from the fact that they're not needed). llvm-svn: 221301
2014-11-05 05:57:32 +08:00
# CHECK-NOT: Name: __compact_unwind