summaryrefslogtreecommitdiffstats
path: root/Tests/Cuda/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* CUDA: Do not device link if CUDA is not an enabled languageRobert Maynard2019-07-011-0/+1
| | | | | | | | | | | | | Checks added in commit 81b4d10d8f (CUDA: More exhaustive checks to determine when to do device linking, 2019-05-09, v3.15.0-rc1~82^2) assumed that CUDA properties would be set only if CUDA is enabled. We cannot do a device link step if we do not have the CUDA language enabled. This was discovered as some projects unconditionally set CUDA properties such as `CUDA_RESOLVE_DEVICE_SYMBOLS` even when the CUDA language has not been enabled. Fixes: #19432
* CUDA: Add test for device linking when host linking uses threadsRobert Maynard2018-10-241-0/+1
| | | | | | | | | Convert the `CudaOnly.LinkSystemDeviceLibraries` test to a new `Cuda.ProperDeviceLibraries` test. The former covered only the `cublas_device` library which is removed by CUDA 10. Extend the new test to also cover various cases of using threads. Issue: #18008
* CUDA: Fix CUDA_STANDARD selection via cxx_std_11 with CXX_STANDARDRobert Maynard2017-12-151-0/+1
| | | | | | | | | | | When C++ features require a certain C++/CUDA level, verify or update the standard level target property for each language independently. While at it, add missing rejection of invalid `CUDA_STANDARD` property values. Co-Author: Brad King <brad.king@kitware.com> Fixes: #17519
* Tests: Add case for CUDA with C but not C++Brad King2017-02-141-0/+1
| | | | An executable using CUDA and C should link as CUDA.
* CUDA: Detect the toolkit include directoriesRobert Maynard2017-02-101-0/+1
| | | | | The `nvcc -v` output provides what include directories need to be added to use the CUDA toolkit from other languages ( C/C++ ).
* CUDA: Test that CUDA flags are used when device linking executables.Robert Maynard2017-01-121-0/+1
|
* CUDA: Add tests to verify CUDA compiler works properly.Robert Maynard2016-11-141-0/+4
generated by cgit v0.12 at 2025-02-15 06:09:08 (GMT)