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/sectalign.yaml

81 lines
2.6 KiB
YAML
Raw Normal View History

Replace -flavor {gnu,darwin} with ld64.lld or ld.lld. llvm-svn: 325390
2018-02-17 05:16:57 +08:00
# RUN: ld64.lld -arch x86_64 -macosx_version_min 10.8 %s -dylib \
[mach-o] Fix stub generation to work for dylibs and bundles Split up the CRuntimeFile into one part for output types that need an entry point and another part for output types that use stubs. Add file 'test/mach-o/Inputs/libSystem.yaml' for use by test cases that use -dylib and therefore may now need the helper symbol in libSystem.dylib. llvm-svn: 215602
2014-08-14 07:31:07 +08:00
# RUN: -sectalign __DATA __custom 0x800 -sectalign __TEXT __text 0x400 \
Have one version of libSystem for each arch. NFC. An upcoming commit will change how we choose to reference a dylib. Currently dylibs are only given an LC_LOAD_DYLIB in the final image if an atom is used. This is different from ld64 which adds the load command when the dylib is referenced on the cmdline. In order to change this behaviour, we need libSystem.yaml to actually contain a mach header so that it is parsed as a dylib, instead of currently being parsed as a normalised file. To get a mach header, we also require an arch, so now we have one libsystem per arch and all the tests have been updated to choose the correct one. llvm-svn: 278372
2016-08-12 02:08:59 +08:00
# RUN: %p/Inputs/x86_64/libSystem.yaml -o %t \
[mach-o] Add support for -sectalign option The -sectalign option is used to increase the alignment required for a section. It required some reworking of how the __TEXT segment is laid out because that segment also contains the mach_header and load commands. And the size of load commands depend on the number of segments, sections, and dependent dylibs used. Using this option will simplify some future test cases because the final address of code can be pinned down, making tests of its content easier. llvm-svn: 214268
2014-07-30 08:58:06 +08:00
# RUN: && llvm-readobj -sections %t | FileCheck %s
#
# Test -sectalign option on __text and a custom section.
#
--- !mach-o
arch: x86_64
file-type: MH_OBJECT
flags: [ MH_SUBSECTIONS_VIA_SYMBOLS ]
sections:
- segment: __TEXT
section: __text
type: S_REGULAR
attributes: [ S_ATTR_PURE_INSTRUCTIONS, S_ATTR_SOME_INSTRUCTIONS ]
address: 0x0000000000000000
Remove trailing whitespace characters. llvm-svn: 235897
2015-04-28 01:18:04 +08:00
content: [ 0x55, 0x48, 0x89, 0xE5, 0x8B, 0x05, 0x00, 0x00,
0x00, 0x00, 0x03, 0x05, 0x00, 0x00, 0x00, 0x00,
[mach-o] Add support for -sectalign option The -sectalign option is used to increase the alignment required for a section. It required some reworking of how the __TEXT segment is laid out because that segment also contains the mach_header and load commands. And the size of load commands depend on the number of segments, sections, and dependent dylibs used. Using this option will simplify some future test cases because the final address of code can be pinned down, making tests of its content easier. llvm-svn: 214268
2014-07-30 08:58:06 +08:00
0x5D, 0xC3 ]
relocations:
- offset: 0x0000000C
type: X86_64_RELOC_SIGNED
length: 2
pc-rel: true
extern: true
symbol: 1
- offset: 0x00000006
type: X86_64_RELOC_SIGNED
length: 2
pc-rel: true
extern: true
symbol: 2
- segment: __DATA
section: __data
type: S_REGULAR
attributes: [ ]
alignment: 2
address: 0x0000000000000014
content: [ 0x0A, 0x00, 0x00, 0x00 ]
- segment: __DATA
section: __custom
type: S_REGULAR
attributes: [ ]
alignment: 2
address: 0x0000000000000018
content: [ 0x0A, 0x00, 0x00, 0x00 ]
global-symbols:
- name: _a
type: N_SECT
scope: [ N_EXT ]
sect: 2
value: 0x0000000000000014
- name: _b
type: N_SECT
scope: [ N_EXT ]
sect: 3
value: 0x0000000000000018
- name: _get
type: N_SECT
scope: [ N_EXT ]
sect: 1
value: 0x0000000000000000
...
# CHECK: Name: __text (5F 5F 74 65 78 74 00 00 00 00 00 00 00 00 00 00)
# CHECK: Segment: __TEXT (5F 5F 54 45 58 54 00 00 00 00 00 00 00 00 00 00)
# CHECK: Address: 0xC00
# CHECK: Name: __data (5F 5F 64 61 74 61 00 00 00 00 00 00 00 00 00 00)
# CHECK: Segment: __DATA (5F 5F 44 41 54 41 00 00 00 00 00 00 00 00 00 00)
# CHECK: Address: 0x1000
# CHECK: Name: __custom (5F 5F 63 75 73 74 6F 6D 00 00 00 00 00 00 00 00)
# CHECK: Segment: __DATA (5F 5F 44 41 54 41 00 00 00 00 00 00 00 00 00 00)
# CHECK: Address: 0x1800