summaryrefslogtreecommitdiffstats
path: root/llvm/test
diff options
context:
space:
mode:
authorJordan Rupprecht <rupprecht@google.com>2019-06-12 18:41:27 +0000
committerJordan Rupprecht <rupprecht@google.com>2019-06-12 18:41:27 +0000
commit146a154e610b5326911d8e66c3d7cfaf3886218e (patch)
treee6f161b0c04042a85edcca5b982ccb0ca8affc5c /llvm/test
parentc69cc8425378a6ce08d6fe8dc0f468f7e983bc60 (diff)
downloadbcm5719-llvm-146a154e610b5326911d8e66c3d7cfaf3886218e.tar.gz
bcm5719-llvm-146a154e610b5326911d8e66c3d7cfaf3886218e.zip
[llvm-ar][test] Relax lit directory assumptions in thin-archive.test
Summary: thin-archive.test assumes the Output/<testname> structure that lit creates. Rewrite the test in a way that still tests the same thing (creating via relative path and adding via absolute path) but doesn't assume this specific lit structure, making it possible to run in a lit emulator. Reviewers: gbreynoo Reviewed By: gbreynoo Subscribers: llvm-commits, bkramer Tags: #llvm Differential Revision: https://reviews.llvm.org/D62930 llvm-svn: 363189
Diffstat (limited to 'llvm/test')
-rw-r--r--llvm/test/tools/llvm-ar/thin-archive.test12
1 files changed, 6 insertions, 6 deletions
diff --git a/llvm/test/tools/llvm-ar/thin-archive.test b/llvm/test/tools/llvm-ar/thin-archive.test
index 8d9543b6869..fca8e117623 100644
--- a/llvm/test/tools/llvm-ar/thin-archive.test
+++ b/llvm/test/tools/llvm-ar/thin-archive.test
@@ -12,15 +12,15 @@ RUN: llvm-ar dT %t/absolute-1.ar delete.o
RUN: FileCheck -input-file=%t/absolute-1.ar --check-prefixes=THIN,CHECK %s -DPATH=%/t/
RUN: llvm-ar t %t/absolute-1.ar | FileCheck %s -DPATH=%/t/
-Test that modules can be added with absolute paths when the archive is created using a relative path
+These tests must be run in %t/foo. cd %t is included on each line to make debugging this test case easier.
-RUN: llvm-ar rTc Output/%basename_t.tmp/absolute-2.ar %t/foo/elf.o %t/delete.o %t/foo/bar/elf.o
-RUN: llvm-ar dT Output/%basename_t.tmp/absolute-2.ar %t/delete.o
+Test that modules can be added with absolute paths when the archive is created using a relative path
-RUN: FileCheck -input-file=%t/absolute-2.ar --check-prefixes=THIN,CHECK %s -DPATH=%/t/
-RUN: llvm-ar t %t/absolute-2.ar | FileCheck %s -DPATH=%/t/
+RUN: cd %t/foo && llvm-ar rTc bar/absolute-2.ar %t/foo/elf.o %t/delete.o %t/foo/bar/elf.o
+RUN: cd %t/foo && llvm-ar dT bar/absolute-2.ar %t/delete.o
-These tests must be run in %t/foo. cd %t is included on each line to make debugging this test case easier.
+RUN: FileCheck -input-file=%t/foo/bar/absolute-2.ar --check-prefixes=THIN,CHECK %s -DPATH=%/t/
+RUN: llvm-ar t %t/foo/bar/absolute-2.ar | FileCheck %s -DPATH=%/t/
Test that modules can be added with relative paths when the archive is created using a relative path
OpenPOWER on IntegriCloud