maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Driver/linker-opts.c

24 lines
966 B
C
Raw Normal View History

Mark -Xclang as being a compilation-only option so that the clang driver doesn't warn if it's passed to a link action. This matches the behavior for most other compilation-only options (including things like -f flags), and is necessary to suppress warnings on systems like cmake that always pass all compile flags to the linker. llvm-svn: 266695
2016-04-19 07:12:59 +08:00
// RUN: rm -rf %t
// RUN: mkdir %t
//
[clang] Get rid of "%T" expansions The %T lit expansion expands to a common directory shared between all the tests in the same directory, which is unexpected and unintuitive, and more importantly, it's been a source of subtle race conditions and flaky tests. In https://reviews.llvm.org/D35396, it was agreed that it would be best to simply ban %T and only keep %t, which is unique to each test. When a test needs a temporary directory, it can just create one using mkdir %t. This patch removes %T in clang. Differential Revision: https://reviews.llvm.org/D36437 llvm-svn: 310950
2017-08-16 03:47:06 +08:00
// RUN: env LIBRARY_PATH=%t/test1 %clang -x c %s -### 2>&1 | FileCheck %s
[driver] Older versions of ld expect '-L<dir>' not '-L <dir>'. In Xcode4 and later, '-L <dir>' is allowed, but rewrite these in the driver as '-L<dir>' to maintain backward compatibility. The same is true for the -I option. rdar://12366753 llvm-svn: 167054
2012-10-31 05:42:09 +08:00
// CHECK: "-L{{.*}}/test1"
test/Driver/linker-opts.c: Mark as XFAIL:cygming, using gcc linker driver. It should be aware of LIBRARY_PATH. llvm-svn: 152896
2012-03-16 13:31:24 +08:00
// GCC driver is used as linker on cygming. It should be aware of LIBRARY_PATH.
clang/test/Driver/linker-opts.c: Fix XFAIL that I removed win32. Sorry for my 3rd commit :( llvm-svn: 169827
2012-12-11 15:23:52 +08:00
// XFAIL: win32
clang/test/Driver: Introduce the feature "clang-driver", set if gcc driver is not used. It is not set at targetting cygming. See PR12920. llvm-svn: 169824
2012-12-11 15:06:09 +08:00
// REQUIRES: clang-driver
LIBRARY_PATH environment variable should only be supported on a native compiler. llvm-svn: 197490
2013-12-17 19:11:25 +08:00
// REQUIRES: native
Support LIBRARY_PATH on all Darwin targets. r197490 changed the behavior of LIBRARY_PATH to try to match GCC's behavior for cross compilers and make clang work better on "bare metal" targets. Unfortunately that change is breaking a number of MacPorts projects because the LIBRARY_PATH environment variable is being ignored when compiling on a 64-bit host for a 32-bit target. Because the host and target architectures differ, isCrossCompiling returns true. This does not make sense for Darwin, where multiple architectures are supported natively via "fat" Mach-O slices and where development is generally done against SDKs regardless. This patch fixes the problem by overriding isCrossCompiling to return false for Darwin toolchains. llvm-svn: 214208
2014-07-30 04:17:52 +08:00
// Make sure that LIBRARY_PATH works for both i386 and x86_64 on Darwin.
[clang] Get rid of "%T" expansions The %T lit expansion expands to a common directory shared between all the tests in the same directory, which is unexpected and unintuitive, and more importantly, it's been a source of subtle race conditions and flaky tests. In https://reviews.llvm.org/D35396, it was agreed that it would be best to simply ban %T and only keep %t, which is unique to each test. When a test needs a temporary directory, it can just create one using mkdir %t. This patch removes %T in clang. Differential Revision: https://reviews.llvm.org/D36437 llvm-svn: 310950
2017-08-16 03:47:06 +08:00
// RUN: env LIBRARY_PATH=%t/test1 %clang -target x86_64-apple-darwin %s -### 2>&1 | FileCheck %s
// RUN: env LIBRARY_PATH=%t/test1 %clang -target i386-apple-darwin %s -### 2>&1 | FileCheck %s
Mark -Xclang as being a compilation-only option so that the clang driver doesn't warn if it's passed to a link action. This matches the behavior for most other compilation-only options (including things like -f flags), and is necessary to suppress warnings on systems like cmake that always pass all compile flags to the linker. llvm-svn: 266695
2016-04-19 07:12:59 +08:00
//
// Make sure that we don't warn on unused compiler arguments.
// RUN: %clang -Xclang -I. -x c %s -c -o %t/tmp.o
// RUN: %clang -Xclang -I. %t/tmp.o -o %t/tmp -### 2>&1 | FileCheck %s --check-prefix=NO-UNUSED
// NO-UNUSED-NOT: warning:{{.*}}unused
//
// Make sure that we do warn in other cases.
// RUN: %clang %s -lfoo -c -o %t/tmp2.o -### 2>&1 | FileCheck %s --check-prefix=UNUSED
// UNUSED: warning:{{.*}}unused