summaryrefslogtreecommitdiffstats
path: root/clang/test/Driver/arm-compiler-rt.c
Commit message (Collapse)AuthorAgeFilesLines
* Fix driver tests when `LLVM_ENABLE_PER_TARGET_RUNTIME_DIR` is `ON`Serge Pavlov2019-10-031-7/+28
| | | | | | | | | | | | | | | | Some Driver tests relied on the default resource direcory having per-os per-arch subdirectory layout, and when clang is built with `-DLLVM_ENABLE_PER_TARGET_RUNTIME_DIR=ON`, those test fail, because clang by default assumes per-target subdirectories. Explicitly set `-resource-dir` flag to point to a tree with per-os per-arch layout. See also: D45604, D62469 Differential Revision: https://reviews.llvm.org/D66981 Patch by Sergej Jaskiewicz <jaskiewiczs@icloud.com>. llvm-svn: 373565
* Revert "Driver: use the canonical static library naming"Saleem Abdulrasool2016-08-311-1/+1
| | | | | | | | This breaks chromium and its unclear if this is actually a modern convention. This reverts SVN r280169. llvm-svn: 280281
* Driver: use the canonical static library namingSaleem Abdulrasool2016-08-301-1/+1
| | | | | | | | | | On Windows, static libraries are named lib<name>.lib while import libraries are named <name>.lib. Use the appropriate naming on itanium and msvc environments. This is setup properly so that if a dynamic builtins is used on Windows, it would do the right thing, although this is not currently wired through the driver (i.e. there is no equivalent to -{shared,static}-gcc). llvm-svn: 280169
* clang/test/Driver/arm-compiler-rt.c: Relax expressions for dos path.NAKAMURA Takumi2015-09-261-7/+7
| | | | llvm-svn: 248666
* Driver: support ARM/HF on a single toolchainSaleem Abdulrasool2015-09-261-0/+21
ARM EABI adds target attributes to the object file. Amongst the attributes that are emitted is the VFP argument passing (Hard vs Soft). The linker is responsible for checking these attributes and erroring on mismatches. This causes problems for the compiler-rt builtins when targeting both hard and soft. Because both of these options name the builtins compiler-rt component the same (libclang_rt.builtins-arm.a or libclang_rt.builtins-arm-android). GCC is able to get away with this as it does one target per toolchain. This changes the naming convention for the ARM compiler-rt builtins to differentiate between HF and Soft. Although this means that compiler-rt may be duplicated, it enables supporting both variants from a single toolchain. A similar approach is taken by the Darwin toolchain, naming the library to differentiate between the calling conventions. llvm-svn: 248649
OpenPOWER on IntegriCloud