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/env.c

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

30 lines
1.4 KiB
C
Raw Normal View History

Add a test that ensures the Clang driver behaves itself when the PATH environment variable is changed to strange things out from under it. Prior to r223099 in LLVM, these test cases would crash in various ways (assert fails, stack exhaustion, etc.). llvm-svn: 223100
2014-12-02 08:53:20 +08:00
// These tests try to ensure that the driver operates reasonably when run with
// a strange environment. Unfortunately, it requires a normal shell and the
Enable passing clang tests on Windows/MSYS. llvm-svn: 243236
2015-07-26 12:36:39 +08:00
// 'env' command that understands arguments, unlike the LIT built-in env.
Add a test that ensures the Clang driver behaves itself when the PATH environment variable is changed to strange things out from under it. Prior to r223099 in LLVM, these test cases would crash in various ways (assert fails, stack exhaustion, etc.). llvm-svn: 223100
2014-12-02 08:53:20 +08:00
//
// REQUIRES: shell
// The PATH variable is heavily used when trying to find a linker.
Preserve LD_LIBRARY_PATH when using the 'env' command In many Linux environments (and similar), just-built applications won't run correctly without making use of the current LD_LIBRARY_PATH environmental variable in order to find dynamic libraries. Propagate it through the 'env' command (hopefully this works on all platforms). llvm-svn: 223219
2014-12-03 16:19:17 +08:00
// RUN: env -i LC_ALL=C LD_LIBRARY_PATH="$LD_LIBRARY_PATH" \
// RUN: %clang -no-canonical-prefixes %s -### -o %t.o 2>&1 \
Add a test that ensures the Clang driver behaves itself when the PATH environment variable is changed to strange things out from under it. Prior to r223099 in LLVM, these test cases would crash in various ways (assert fails, stack exhaustion, etc.). llvm-svn: 223100
2014-12-02 08:53:20 +08:00
// RUN: --target=i386-unknown-linux \
// RUN: --sysroot=%S/Inputs/basic_linux_tree \
[Driver] Fix tests failing in per-target multiarch layout These failures were revealed by b4537c3f51bc6c011ddd9c10b80043ac4ce16a01. Differential Revision: https://reviews.llvm.org/D101348
2021-04-27 17:15:37 +08:00
// RUN: --rtlib=platform \
Fix clash of gcc toolchains in driver regression tests. For some regression tests the path to the right toolchain is specified using the -sysroot switch. However, if clang was configured with a custom gcc toolchain (either by using GCC_INSTALL_PREFIX in cmake or the equivalent configure command), the path to the custom gcc toolchain path takes precedence to the one specified by sysroot. This causes several regression tests to fail as they will be using an unexpected path. This patch fixes this issue by adding --gcc-toolchain='' to all tests that rely on that. The empty string causes the driver to pick the path from sysroot instead. llvm-svn: 225182
2015-01-06 01:07:42 +08:00
// RUN: --gcc-toolchain="" \
Add a test that ensures the Clang driver behaves itself when the PATH environment variable is changed to strange things out from under it. Prior to r223099 in LLVM, these test cases would crash in various ways (assert fails, stack exhaustion, etc.). llvm-svn: 223100
2014-12-02 08:53:20 +08:00
// RUN: | FileCheck --check-prefix=CHECK-LD-32 %s
//
Preserve LD_LIBRARY_PATH when using the 'env' command In many Linux environments (and similar), just-built applications won't run correctly without making use of the current LD_LIBRARY_PATH environmental variable in order to find dynamic libraries. Propagate it through the 'env' command (hopefully this works on all platforms). llvm-svn: 223219
2014-12-03 16:19:17 +08:00
// RUN: env -i LC_ALL=C PATH="" LD_LIBRARY_PATH="$LD_LIBRARY_PATH" \
// RUN: %clang -no-canonical-prefixes %s -### -o %t.o 2>&1 \
Add a test that ensures the Clang driver behaves itself when the PATH environment variable is changed to strange things out from under it. Prior to r223099 in LLVM, these test cases would crash in various ways (assert fails, stack exhaustion, etc.). llvm-svn: 223100
2014-12-02 08:53:20 +08:00
// RUN: --target=i386-unknown-linux \
// RUN: --sysroot=%S/Inputs/basic_linux_tree \
[Driver] Fix tests failing in per-target multiarch layout These failures were revealed by b4537c3f51bc6c011ddd9c10b80043ac4ce16a01. Differential Revision: https://reviews.llvm.org/D101348
2021-04-27 17:15:37 +08:00
// RUN: --rtlib=platform \
Fix clash of gcc toolchains in driver regression tests. For some regression tests the path to the right toolchain is specified using the -sysroot switch. However, if clang was configured with a custom gcc toolchain (either by using GCC_INSTALL_PREFIX in cmake or the equivalent configure command), the path to the custom gcc toolchain path takes precedence to the one specified by sysroot. This causes several regression tests to fail as they will be using an unexpected path. This patch fixes this issue by adding --gcc-toolchain='' to all tests that rely on that. The empty string causes the driver to pick the path from sysroot instead. llvm-svn: 225182
2015-01-06 01:07:42 +08:00
// RUN: --gcc-toolchain="" \
Add a test that ensures the Clang driver behaves itself when the PATH environment variable is changed to strange things out from under it. Prior to r223099 in LLVM, these test cases would crash in various ways (assert fails, stack exhaustion, etc.). llvm-svn: 223100
2014-12-02 08:53:20 +08:00
// RUN: | FileCheck --check-prefix=CHECK-LD-32 %s
//
// CHECK-LD-32-NOT: warning:
// CHECK-LD-32: "{{.*}}ld{{(.exe)?}}" "--sysroot=[[SYSROOT:[^"]+]]"
[Driver] Fix architecture triplets and search paths for Linux x32 Currently, support for the x32 ABI is handled as a multilib to the x86_64 target only. However, full self-hosting x32 systems treating it as a separate architecture with its own architecture triplets as well as search paths exist as well, in Debian's x32 port and elsewhere. This adds the missing architecture triplets and search paths so that clang can work as a native compiler on x32, and updates the tests so that they pass when using an x32 libdir suffix. Additionally, we would previously also assume that objects from any x86_64-linux-gnu GCC installation could be used to target x32. This changes the logic so that only GCC installations that include x32 support are used when targetting x32, meaning x86_64-linux-gnux32 GCC installations, and x86_64-linux-gnu and i686-linux-gnu GCC installations that include x32 multilib support. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D52050
2021-04-01 16:47:56 +08:00
// CHECK-LD-32: "{{.*}}/usr/lib/gcc/i386-unknown-linux/10.2.0{{/|\\\\}}crtbegin.o"
// CHECK-LD-32: "-L[[SYSROOT]]/usr/lib/gcc/i386-unknown-linux/10.2.0"
// CHECK-LD-32: "-L[[SYSROOT]]/usr/lib/gcc/i386-unknown-linux/10.2.0/../../../../i386-unknown-linux/lib"
Add a test that ensures the Clang driver behaves itself when the PATH environment variable is changed to strange things out from under it. Prior to r223099 in LLVM, these test cases would crash in various ways (assert fails, stack exhaustion, etc.). llvm-svn: 223100
2014-12-02 08:53:20 +08:00
// CHECK-LD-32: "-L[[SYSROOT]]/lib"
// CHECK-LD-32: "-L[[SYSROOT]]/usr/lib"