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/exe-offsets.yaml

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

46 lines
1015 B
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 %s -o %t -e start %p/Inputs/x86_64/libSystem.yaml
[test] Change llvm-readobj -long-option to --long-option or well-known short options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
2019-05-01 13:49:01 +08:00
# RUN: llvm-readobj --sections %t | FileCheck %s
MachO: calculate segment offsets in final MachO files properly. Because of how we were calculating fileOffset and fileSize for segments, most ended up at a single offset in a finalised MachO file. This meant the data often didn't even get written in the final object, let alone where it would be useful. llvm-svn: 212030
2014-06-30 17:49:30 +08:00
# Make sure data gets put at offset
--- !native
defined-atoms:
- name: start
scope: global
content: [ 90 ]
- name: _s1
type: data
content: [ 31, 32, 33, 34 ]
- name: _s2
type: zero-fill
size: 8192
- name: _s3
type: zero-fill
size: 100
- name: _s4
type: data
content: [ 01 ]
[mach-o] refactor KindHandler into ArchHandler and simplify passes. All architecture specific handling is now done in the appropriate ArchHandler subclass. The StubsPass and GOTPass have been simplified. All architecture specific variations in stubs are now encoded in a table which is vended by the current ArchHandler. llvm-svn: 213187
2014-07-17 03:49:02 +08:00
MachO: calculate segment offsets in final MachO files properly. Because of how we were calculating fileOffset and fileSize for segments, most ended up at a single offset in a finalised MachO file. This meant the data often didn't even get written in the final object, let alone where it would be useful. llvm-svn: 212030
2014-06-30 17:49:30 +08:00
# CHECK-LABEL: Section {
# CHECK: Name: __text
# CHECK: Segment: __TEXT
# CHECK: Size: 0x1
# CHECK: Offset: 0
# CHECK-LABEL: Section {
# CHECK: Name: __data
# CHECK: Segment: __DATA
# CHECK: Size: 0x5
# CHECK: Offset: 4096
# CHECK-LABEL: Section {
[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: calculate segment offsets in final MachO files properly. Because of how we were calculating fileOffset and fileSize for segments, most ended up at a single offset in a finalised MachO file. This meant the data often didn't even get written in the final object, let alone where it would be useful. llvm-svn: 212030
2014-06-30 17:49:30 +08:00
# CHECK: Segment: __DATA
[mach-o] zero-fill sections have no file offset In mach-o, sections of type S_ZEROFILL are special cased and to always have their section.offset field be zero. llvm-svn: 222202
2014-11-18 08:30:29 +08:00
# CHECK: Size: 0x2064
# CHECK: Offset: 0