summaryrefslogtreecommitdiffstats
path: root/clang/test/Driver/mips-mti-linux.c
Commit message (Collapse)AuthorAgeFilesLines
* Default to -fuse-init-arrayFangrui Song2019-12-121-2/+2
| | | | | | | | | | | | | | | | | | | Very few ELF platforms still use .ctors/.dtors now. Linux (glibc: 1999-07), DragonFlyBSD, FreeBSD (2012-03) and Solaris have supported .init_array for many years. Some architectures like AArch64/RISC-V default to .init_array . GNU ld and gold can even convert .ctors to .init_array . It makes more sense to flip the CC1 default, and only uses -fno-use-init-array on platforms that don't support .init_array . For example, OpenBSD did not support DT_INIT_ARRAY before Aug 2016 (https://github.com/openbsd/src/commit/86fa57a2792c6374b0849dd7b818a11e676e60ba) I may miss some ELF platforms that still use .ctors, but their maintainers can easily diagnose such problems. Reviewed By: rnk Differential Revision: https://reviews.llvm.org/D71393
* Try to fix this clang driver test case after r340709.Chandler Carruth2018-08-271-2/+2
| | | | | | | | If any of the bots complain about this, I'll just revert. This test case is essentially trying to test the exact change made, but I think this matches the intent of the patch in question. llvm-svn: 340727
* Fix tests with CLANG_DEFAULT_LINKERJonas Hahnfeld2017-01-081-2/+2
| | | | | | | | | I originally requested this to be tested in D25263 but in the end forgot to make sure that it was done. Differential Revision: https://reviews.llvm.org/D28289 llvm-svn: 291389
* Support setting default value for -rtlib at build timeJonas Hahnfeld2016-07-271-2/+2
| | | | | | | | | | | | | | | | | This patch introduces a new cmake variable: CLANG_DEFAULT_RTLIB, thru which we can specify a default value for -rtlib (libgcc or compiler-rt) at build time, just like how we set the default C++ stdlib thru CLANG_DEFAULT_CXX_STDLIB. With these two options, we can configure clang to build binaries on Linux that have no runtime dependence on any gcc libs (libstdc++ or libgcc_s). Patch by Lei Zhang! Differential Revision: https://reviews.llvm.org/D22663 llvm-svn: 276848
* Fix the failing windows clang unit tests. NFCSumanth Gundapaneni2015-12-161-0/+1
| | | | | | | | | | Some tests are missing the {{(.exe)?}} suffix on the exectables which the FileCheck is grepping for. This will ensure, the lit tests are clean on windows Differential Revision: http://reviews.llvm.org/D15579 llvm-svn: 255804
* [mips] Do not add arch name in the compiler-rt's components.Vasileios Kalintiris2015-11-161-1/+1
| | | | | | | Instead, use the constant "mips" since the libraries are already placed under the multilib's OS suffix. llvm-svn: 253214
* Update for the gnu flavor being renamed to old-gnu.Rafael Espindola2015-11-161-2/+2
| | | | llvm-svn: 253191
* clang/test/Driver/mips-mti-linux.c: Tweak to match DOSish paths.NAKAMURA Takumi2015-11-131-4/+2
| | | | llvm-svn: 253011
* clang/test/Driver/mips-mti-linux.c: Remove XFAIL. It shouldn't fail for ↵NAKAMURA Takumi2015-11-121-1/+1
| | | | | | | | targeting win32. I will remove REQUIRES later. llvm-svn: 252972
* Re-recommit: Add support for the new mips-mti-linux toolchain.Vasileios Kalintiris2015-11-121-0/+44
| | | | | | | | Last time, this caused two Windows buildbots and a single ARM buildbot to fail. I XFAIL'd the failing test on win32,win64 machines in order to see if the ARM buildbot complains again. llvm-svn: 252901
* Revert "[mips] Add support for the new mips-mti-linux toolchain."Vasileios Kalintiris2015-10-301-45/+0
| | | | | | | This reverts commits r251633. I'll investigate the test failure off trunk in order to keep the buildbots clean. llvm-svn: 251698
* Revert "Try to run and investigate the mips-mti-linux.c test failure on ARM ↵Renato Golin2015-10-301-7/+6
| | | | | | | | | buildbots." This reverts commit r251695. Debug is meant to be done off tree, not use the buildbots experiments. I'll help investigate this problem off trunk. llvm-svn: 251696
* Try to run and investigate the mips-mti-linux.c test failure on ARM buildbots.Vasileios Kalintiris2015-10-301-6/+7
| | | | | | | | This should be a NFC for every toolchain other than mips-mti-linux (where we print the list of directories searched for crt files). It will soon be reverted once we hit the clang-cmake-armv7-a15-selfhost-neon buildbot. llvm-svn: 251695
* [mips] Add support for the new mips-mti-linux toolchain.Vasileios Kalintiris2015-10-291-0/+45
| | | | | | | | | | The original commit in r249137 added the mips-mti-linux toolchain. However, the newly added tests of that commit failed in few buildbots. This commit re-applies the original changes but XFAILs the test file which caused the buildbot failures. This will allow us to examine what's going wrong without having to commit/revert large changes. llvm-svn: 251633
* Remove support for the mips-mti-linux toolchain.Vasileios Kalintiris2015-10-051-42/+0
| | | | | | | There are two remaining buildbot failures that we'll have to investigate before submitting this again. llvm-svn: 249298
* Fix test failure on Windows buildbots for the mips-mti-linux toolchain.Vasileios Kalintiris2015-10-051-6/+6
| | | | | | | Try to make the Windows buildbots happy by fixing the regexes that match the paths to CRT files. llvm-svn: 249296
* Re-commit "Add support for the new mips-mti-linux toolchain."Vasileios Kalintiris2015-10-051-0/+42
| | | | | | | | | | | r249137 added support for the new mips-mti-linux toolchain. However, the new tests of that commit, broke some buildbots because they didn't use the correct regular expressions to capture the filename of Clang & LLD. This commit re-applies the changes of r249137 and fixes the tests in r249137 in order to match the filenames of the Clang and LLD executable. llvm-svn: 249294
* Revert "Add support for the new mips-mti-linux toolchain."Vasileios Kalintiris2015-10-021-42/+0
| | | | | | | This reverts commit r249137 because it broke the Windows buildbots and a Linux buildbot for LLD. llvm-svn: 249141
* Add support for the new mips-mti-linux toolchain.Vasileios Kalintiris2015-10-021-0/+42
Summary: This new toolchain uses primarily LLVM-based tools, eg. compiler-rt, lld, libcxx, etc. Because of this, it doesn't require neither an existing GCC installation nor a GNU environment. Ideally, in a follow-up patch we would like to add a new --{llvm|clang}-toolchain option (similar to --gcc-toolchain) in order to allow the use of this toolchain with independent Clang builds. For the time being, we use the --sysroot option just to test the correctness of the paths generated by the driver. Reviewers: atanasyan, dsanders, rsmith Subscribers: jfb, tberghammer, danalbert, srhines, dschuff, cfe-commits Differential Revision: http://reviews.llvm.org/D13340 llvm-svn: 249137
OpenPOWER on IntegriCloud