We have a mix of substituted lld (`%lld`) and hard-coded lld (`ld64.lld`) commands. When testing with different versions of LLD, this would require going into every place where lld is hard-coded and changing that. If we centralize it, this'll only require us to modify it in only one place and will make it easy to run the same test suite. Plus, this will make it be consistent with how we write other tests. Reviewed By: #lld-macho, int3, oontvoo Differential Revision: https://reviews.llvm.org/D119394
20 lines
658 B
Plaintext
20 lines
658 B
Plaintext
REQUIRES: x86
|
|
REQUIRES: system-darwin
|
|
|
|
RUN: mkdir -p %t1 %t2
|
|
|
|
RUN: not %no-arg-lld -arch x86_64 -platform_version macos 10.5 11.0 -v -L%t1 -F%t2 2>&1 | FileCheck -DLDIR=%t1 -DFDIR=%t2 %s
|
|
CHECK: Library search paths:
|
|
CHECK-NEXT: [[LDIR]]
|
|
CHECK-NEXT: /usr/lib
|
|
CHECK: Framework search paths:
|
|
CHECK-NEXT: [[FDIR]]
|
|
CHECK-NEXT: /Library/Frameworks
|
|
CHECK-NEXT: /System/Library/Frameworks
|
|
|
|
RUN: not %no-arg-lld -arch x86_64 -platform_version macos 10.5 11.0 -v -L%t1 -F%t2 -Z 2>&1 | FileCheck -DLDIR=%t1 -DFDIR=%t2 --check-prefix=CHECK_Z %s
|
|
CHECK_Z: Library search paths:
|
|
CHECK_Z-NEXT: [[LDIR]]
|
|
CHECK_Z-NEXT: Framework search paths:
|
|
CHECK_Z-NEXT: [[FDIR]]
|