File: linker-script-in-search-path.s

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (19 lines) | stat: -rw-r--r-- 808 bytes parent folder | download | duplicates (23)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
# REQUIRES: x86
# Check that we fall back to search paths if a linker script was not found
# This behaviour matches ld.bfd and various projects appear to rely on this

# RUN: llvm-mc -filetype=obj -triple=x86_64-unknown-linux %s -o %t.o
# RUN: rm -rf %t.dir && mkdir -p %t.dir
# RUN: echo 'OUTPUT("%t.out")' > %t.dir/script
# RUN: ld.lld -T%t.dir/script %t.o
# RUN: llvm-readobj %t.out | FileCheck %s
# CHECK: Format: elf64-x86-64

# If the linker script specified with -T is missing we should emit an error
# RUN: not ld.lld -Tscript %t.o 2>&1 | FileCheck %s -check-prefix ERROR
# ERROR: error: cannot find linker script {{.*}}script

# But if it exists in the search path we should fall back to that instead:
# RUN: rm %t.out
# RUN: ld.lld -L %t.dir -Tscript %t.o
# RUN: llvm-readobj %t.out | FileCheck %s