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/map-file.s

63 lines
3.2 KiB
ArmAsm
Raw Normal View History

Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// REQUIRES: x86
// RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t1.o
// RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %p/Inputs/map-file2.s -o %t2.o
// RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %p/Inputs/map-file3.s -o %t3.o
// RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %p/Inputs/map-file4.s -o %t4.o
// RUN: rm -f %t4.a
// RUN: llvm-ar rc %t4.a %t4.o
Add -print-map and -M options. llvm-svn: 292046
2017-01-15 10:52:34 +08:00
// RUN: ld.lld %t1.o %t2.o %t3.o %t4.a -o %t -M | FileCheck %s
// RUN: ld.lld %t1.o %t2.o %t3.o %t4.a -o %t -print-map | FileCheck %s
// RUN: ld.lld %t1.o %t2.o %t3.o %t4.a -o %t -Map=%t.map
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// RUN: FileCheck %s < %t.map
.global _start
_start:
call baz
.global _Z1fi
_Z1fi:
.cfi_startproc
.cfi_endproc
nop
.weak bar
bar:
.long bar - .
.long zed - .
local:
Print alignment in decimal instead of hexadecimal. Previously, we were printing out something like this for sections/symbols with alignment 16 0000000000201000 0000000000000182 10 .data which I think confusing. I think printing it in decimal is better. Differential Revision: https://reviews.llvm.org/D29258 llvm-svn: 293685
2017-02-01 04:42:34 +08:00
.comm common,4,16
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK: Address Size Align Out In File Symbol
Revert "Add terminator to .eh_frame sections" This reverts commit r296378. I am pretty sure this is incorrect. In particular, for just .cfi_startproc nop .cfi_endproc We now add an extra 4 zeros that neither bfd nor gold add. llvm-svn: 296503
2017-03-01 02:55:08 +08:00
// CHECK-NEXT: 0000000000200158 0000000000000030 8 .eh_frame
// CHECK-NEXT: 0000000000200158 0000000000000030 8 .eh_frame
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 0000000000201000 0000000000000015 4 .text
// CHECK-NEXT: 0000000000201000 000000000000000e 4 .text
Try to fix the windows bots. llvm-svn: 291989
2017-01-14 10:45:53 +08:00
// CHECK-NEXT: 0000000000201000 000000000000000e 4 {{.*}}{{/|\\}}map-file.s.tmp1.o
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 000000000020100e 0000000000000000 0 local
// CHECK-NEXT: 0000000000201005 0000000000000000 0 f(int)
// CHECK-NEXT: 0000000000201000 0000000000000000 0 _start
Try to fix the windows bots. llvm-svn: 291989
2017-01-14 10:45:53 +08:00
// CHECK-NEXT: 0000000000201010 0000000000000002 4 {{.*}}{{/|\\}}map-file.s.tmp2.o
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 0000000000201010 0000000000000000 0 foo
// CHECK-NEXT: 0000000000201011 0000000000000000 0 bar
// CHECK-NEXT: 0000000000201012 0000000000000000 1 .text.zed
Try to fix the windows bots. llvm-svn: 291989
2017-01-14 10:45:53 +08:00
// CHECK-NEXT: 0000000000201012 0000000000000000 1 {{.*}}{{/|\\}}map-file.s.tmp2.o
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 0000000000201012 0000000000000000 0 zed
// CHECK-NEXT: 0000000000201014 0000000000000000 4 .text
Try to fix the windows bots. llvm-svn: 291989
2017-01-14 10:45:53 +08:00
// CHECK-NEXT: 0000000000201014 0000000000000000 4 {{.*}}{{/|\\}}map-file.s.tmp3.o
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 0000000000201014 0000000000000000 0 bah
Try to fix the windows bots. llvm-svn: 291989
2017-01-14 10:45:53 +08:00
// CHECK-NEXT: 0000000000201014 0000000000000001 4 {{.*}}{{/|\\}}map-file.s.tmp4.a(map-file.s.tmp4.o)
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 0000000000201014 0000000000000000 0 baz
Print alignment in decimal instead of hexadecimal. Previously, we were printing out something like this for sections/symbols with alignment 16 0000000000201000 0000000000000182 10 .data which I think confusing. I think printing it in decimal is better. Differential Revision: https://reviews.llvm.org/D29258 llvm-svn: 293685
2017-02-01 04:42:34 +08:00
// CHECK-NEXT: 0000000000202000 0000000000000004 16 .bss
// CHECK-NEXT: 0000000000202000 0000000000000004 16 COMMON
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 0000000000000000 0000000000000008 1 .comment
Replace MergeOutputSection with a synthetic section. With a synthetic merge section we can have, for example, a single .rodata section with stings, fixed sized constants and non merge constants. I can be simplified further by not setting Entsize, but that is probably better done is a followup patch. This should allow some cleanup in the linker script code now that every output section command maps to just one output section. llvm-svn: 294005
2017-02-03 21:06:18 +08:00
// CHECK-NEXT: 0000000000000000 0000000000000008 1 .comment
Implement -Map. The format is not exactly the same as the one in bfd since bfd always follows a linker script and prints it along. llvm-svn: 291958
2017-01-14 05:05:46 +08:00
// CHECK-NEXT: 0000000000000000 00000000000000f0 8 .symtab
// CHECK-NEXT: 0000000000000000 00000000000000f0 8 .symtab
// CHECK-NEXT: 0000000000000000 0000000000000039 1 .shstrtab
// CHECK-NEXT: 0000000000000000 0000000000000039 1 .shstrtab
// CHECK-NEXT: 0000000000000000 000000000000002f 1 .strtab
// CHECK-NEXT: 0000000000000000 000000000000002f 1 .strtab
Return early if writeMapFile failed. This patch adds a test for an invalid output path for -Map option, though that test is not for verifying that we are using error() instead of fatal() in writeMapFile. llvm-svn: 292336
2017-01-18 11:34:38 +08:00
// RUN: not ld.lld %t1.o %t2.o %t3.o %t4.a -o %t -Map=/ 2>&1 \
// RUN: | FileCheck -check-prefix=FAIL %s
// FAIL: cannot open /