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/gcc-toolchain.cpp

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

40 lines
2.1 KiB
C++
Raw Normal View History

Implement a -gcc-toolchain command line option that does the same as configure's --with-gcc-toolchain. The configure option is now just a default value for the command line one. llvm-svn: 150898
2012-02-19 09:38:32 +08:00
// Test that gcc-toolchain option is working correctly
//
[test] Fix Driver/gcc-toolchain.cpp if CLANG_DEFAULT_RTLIB is compiler-rt
2021-03-21 04:24:49 +08:00
/// Without --rtlib=libgcc the driver may pick clang_rt.crtbegin.o if
/// -DCLANG_DEFAULT_RTLIB=compiler-rt.
[test] Add --sysroot= to make gcc-toolchain.cpp stable
2021-03-24 04:32:30 +08:00
// RUN: %clangxx %s -### --target=x86_64-linux-gnu --sysroot= \
[test] Fix Driver/gcc-toolchain.cpp if CLANG_DEFAULT_RTLIB is compiler-rt
2021-03-21 04:24:49 +08:00
// RUN: --gcc-toolchain=%S/Inputs/ubuntu_14.04_multiarch_tree/usr -stdlib=libstdc++ --rtlib=libgcc 2>&1 | \
Revert "Revert "[Driver] Drop obsoleted Ubuntu 11.04 gcc detection"" This reverts commit 243333ef3ec6c1e3910eb442177c2e2e927e6a87.
2021-03-21 00:57:05 +08:00
// RUN: FileCheck %s
Update two options to my proposed syntax for user-facing driver options: -gcc-toolchain foo -> --gcc-toolchain=foo -target foo -> --target=foo I've added legacy aliases for the original spellings. I've updated the canonical tests to check both spellings, and switched all of the -gcc-toolchain usages elsewhere in the test suite to use the new one. I've updated some of the usages of -target to the new syntax, but will finish that in a separate entirely mechanical change once I'm sure this won't get rolled back for some reason (It touches a *huge* number of RUN lines in the test suite unsurprisingly). A nice result is that the three most common flags I end up using when doing cross compiles are all now consistent: --target=, --sysroot=, and --gcc-toolchain=. llvm-svn: 184408
2013-06-20 17:42:40 +08:00
//
// Additionally check that the legacy spelling of the flag works.
[test] Add --sysroot= to make gcc-toolchain.cpp stable
2021-03-24 04:32:30 +08:00
// RUN: %clangxx %s -### --target=x86_64-linux-gnu --sysroot= \
[test] Migrate -gcc-toolchain with space separator to --gcc-toolchain= Space separated driver options are uncommon but Clang traditionally did not do a good job. --gcc-toolchain= is the preferred form.
2021-08-21 06:24:58 +08:00
// RUN: --gcc-toolchain=%S/Inputs/ubuntu_14.04_multiarch_tree/usr -stdlib=libstdc++ --rtlib=libgcc 2>&1 | \
Revert "Revert "[Driver] Drop obsoleted Ubuntu 11.04 gcc detection"" This reverts commit 243333ef3ec6c1e3910eb442177c2e2e927e6a87.
2021-03-21 00:57:05 +08:00
// RUN: FileCheck %s
Clean up, add some documentation, and make this test return to checking the linker toolchainness a bit more thoroughly. It used to work this way, but hit buildbot issues. Hopefully subsequent fixes have addressed those problems, but I'll be watching the bots. llvm-svn: 151090
2012-02-22 05:51:40 +08:00
//
// Test for header search toolchain detection.
Implement a -gcc-toolchain command line option that does the same as configure's --with-gcc-toolchain. The configure option is now just a default value for the command line one. llvm-svn: 150898
2012-02-19 09:38:32 +08:00
// CHECK: "-internal-isystem"
Revert "Revert "[Driver] Drop obsoleted Ubuntu 11.04 gcc detection"" This reverts commit 243333ef3ec6c1e3910eb442177c2e2e927e6a87.
2021-03-21 00:57:05 +08:00
// CHECK: "[[TOOLCHAIN:[^"]+]]/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8"
Implement a -gcc-toolchain command line option that does the same as configure's --with-gcc-toolchain. The configure option is now just a default value for the command line one. llvm-svn: 150898
2012-02-19 09:38:32 +08:00
// CHECK: "-internal-isystem"
Revert "Revert "[Driver] Drop obsoleted Ubuntu 11.04 gcc detection"" This reverts commit 243333ef3ec6c1e3910eb442177c2e2e927e6a87.
2021-03-21 00:57:05 +08:00
// CHECK: "[[TOOLCHAIN]]/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/x86_64-linux-gnu/c++/4.8"
Implement a -gcc-toolchain command line option that does the same as configure's --with-gcc-toolchain. The configure option is now just a default value for the command line one. llvm-svn: 150898
2012-02-19 09:38:32 +08:00
// CHECK: "-internal-isystem"
Revert "Revert "[Driver] Drop obsoleted Ubuntu 11.04 gcc detection"" This reverts commit 243333ef3ec6c1e3910eb442177c2e2e927e6a87.
2021-03-21 00:57:05 +08:00
// CHECK: "[[TOOLCHAIN]]/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/backward"
Clean up, add some documentation, and make this test return to checking the linker toolchainness a bit more thoroughly. It used to work this way, but hit buildbot issues. Hopefully subsequent fixes have addressed those problems, but I'll be watching the bots. llvm-svn: 151090
2012-02-22 05:51:40 +08:00
//
Skip testing the crtbegin.o, and resume using a single variable for the prefixes. It seems only crtbegin.o uses the strange formatting. llvm-svn: 151094
2012-02-22 06:21:50 +08:00
// Test for linker toolchain detection. Note that only the '-L' flags will use
// the same precise formatting of the path as the '-internal-system' flags
// above, so we just blanket wildcard match the 'crtbegin.o'.
Make the regular expressions in this test more narrow to ensure we're actually matching the write substrings, and stop looking for a leading '/' to try and finish fixing darwin and other hosts. llvm-svn: 150938
2012-02-20 07:09:50 +08:00
// CHECK: "{{[^"]*}}ld{{(.exe)?}}"
Revert "Revert "[Driver] Drop obsoleted Ubuntu 11.04 gcc detection"" This reverts commit 243333ef3ec6c1e3910eb442177c2e2e927e6a87.
2021-03-21 00:57:05 +08:00
// CHECK-SAME: "{{[^"]*}}/usr/lib/gcc/x86_64-linux-gnu/4.8{{/|\\\\}}crtbegin.o"
// CHECK-SAME: "-L[[TOOLCHAIN]]/usr/lib/gcc/x86_64-linux-gnu/4.8"
/// On x86_64, there is an extra usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu but we should not test it.
[Driver] Suppress GCC detection under -B In GCC, if `-B $prefix` is specified, `$prefix` is used to find executable files and startup files. `$prefix/include` is added as an include search directory. Clang overloads -B with GCC installation detection semantics which make the behavior less predictable (due to the "largest GCC version wins" rule) and interact poorly with --gcc-toolchain (--gcc-toolchain can be overridden by -B). * `clang++ foo.cpp` detects GCC installation under `/usr`. * `clang++ --gcc-toolchain=Inputs foo.cpp` detects GCC installation under `Inputs`. * `clang++ -BA --gcc-toolchain=B foo.cpp` detects GCC installation under A and B and the larger version wins. With this patch, only B is used for detection. * `clang++ -BA foo.cpp` detects GCC installation under `A` and `/usr`, and the larger GCC version wins. With this patch `A` is not used for detection. This patch changes -B to drop the GCC detection semantics. Its executable searching semantics are preserved. --gcc-toolchain is the recommended option to specify the GCC installation detection directory. ( Note: Clang detects GCC installation in various target dependent directories. `$sysroot/usr` (sysroot defaults to "") is a common directory used by most targets. Such a directory is expected to contain something like `lib{,32,64}/gcc{,-cross}/$triple`. Clang will then construct library/include paths from the directory. ) Differential Revision: https://reviews.llvm.org/D97993
2021-03-20 06:42:18 +08:00
/// Test we don't detect GCC installation under -B.
[test] Add --sysroot= to make gcc-toolchain.cpp stable
2021-03-24 04:32:30 +08:00
// RUN: %clangxx %s -### --sysroot= 2>&1 \
[Driver] Suppress GCC detection under -B In GCC, if `-B $prefix` is specified, `$prefix` is used to find executable files and startup files. `$prefix/include` is added as an include search directory. Clang overloads -B with GCC installation detection semantics which make the behavior less predictable (due to the "largest GCC version wins" rule) and interact poorly with --gcc-toolchain (--gcc-toolchain can be overridden by -B). * `clang++ foo.cpp` detects GCC installation under `/usr`. * `clang++ --gcc-toolchain=Inputs foo.cpp` detects GCC installation under `Inputs`. * `clang++ -BA --gcc-toolchain=B foo.cpp` detects GCC installation under A and B and the larger version wins. With this patch, only B is used for detection. * `clang++ -BA foo.cpp` detects GCC installation under `A` and `/usr`, and the larger GCC version wins. With this patch `A` is not used for detection. This patch changes -B to drop the GCC detection semantics. Its executable searching semantics are preserved. --gcc-toolchain is the recommended option to specify the GCC installation detection directory. ( Note: Clang detects GCC installation in various target dependent directories. `$sysroot/usr` (sysroot defaults to "") is a common directory used by most targets. Such a directory is expected to contain something like `lib{,32,64}/gcc{,-cross}/$triple`. Clang will then construct library/include paths from the directory. ) Differential Revision: https://reviews.llvm.org/D97993
2021-03-20 06:42:18 +08:00
// RUN: --target=aarch64-suse-linux --gcc-toolchain=%S/Inputs/opensuse_42.2_aarch64_tree/usr | \
// RUN: FileCheck %s --check-prefix=AARCH64
[test] Add --sysroot= to make gcc-toolchain.cpp stable
2021-03-24 04:32:30 +08:00
// RUN: %clangxx %s -### --sysroot= 2>&1 \
[Driver] Suppress GCC detection under -B In GCC, if `-B $prefix` is specified, `$prefix` is used to find executable files and startup files. `$prefix/include` is added as an include search directory. Clang overloads -B with GCC installation detection semantics which make the behavior less predictable (due to the "largest GCC version wins" rule) and interact poorly with --gcc-toolchain (--gcc-toolchain can be overridden by -B). * `clang++ foo.cpp` detects GCC installation under `/usr`. * `clang++ --gcc-toolchain=Inputs foo.cpp` detects GCC installation under `Inputs`. * `clang++ -BA --gcc-toolchain=B foo.cpp` detects GCC installation under A and B and the larger version wins. With this patch, only B is used for detection. * `clang++ -BA foo.cpp` detects GCC installation under `A` and `/usr`, and the larger GCC version wins. With this patch `A` is not used for detection. This patch changes -B to drop the GCC detection semantics. Its executable searching semantics are preserved. --gcc-toolchain is the recommended option to specify the GCC installation detection directory. ( Note: Clang detects GCC installation in various target dependent directories. `$sysroot/usr` (sysroot defaults to "") is a common directory used by most targets. Such a directory is expected to contain something like `lib{,32,64}/gcc{,-cross}/$triple`. Clang will then construct library/include paths from the directory. ) Differential Revision: https://reviews.llvm.org/D97993
2021-03-20 06:42:18 +08:00
// RUN: --target=aarch64-suse-linux -B%S/Inputs/opensuse_42.2_aarch64_tree/usr | \
// RUN: FileCheck %s --check-prefix=NO_AARCH64
// AARCH64: Inputs{{[^"]+}}aarch64-suse-linux/{{[^"]+}}crt1.o"
// NO_AARCH64-NOT: Inputs{{[^"]+}}aarch64-suse-linux/{{[^"]+}}crt1.o"