| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This ensures that we don't add rpath entries to the stubs directory
which would cause runtime loading of the wrong libraries.
|
|\
| |
| |
| |
| |
| |
| |
| | |
6b5f2dbbfe file(REAL_PATH): resolve symlinks before '..' components
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8605
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously REAL_PATH would collapse paths before resolving any symlinks
so if `..` crossed a symlink the output from `REAL_PATH` would be wrong.
It looked like REAL_PATH did this by mistake since it was a side-effect
of ensuring we had an absolute path before resolving symlinks.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
c2601d01d1 FindCUDAToolkit: Fix nvrtc_builtins library name
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robertjmaynard@gmail.com>
Merge-request: !8642
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The lib is named `libnvrtc-builtins.so`, not `libnvrtc_builtins.so`.
Update the change from commit 2a94c762ed (FindCUDAToolkit: Add support
for CUDA::nvrtc_static, 2023-01-20, v3.26.0-rc1~55^2). Apply a fix
similar to commit 9688a8ebc2 (FindCUDAToolkit: Fix
`nvrtc_builtins_static` library name, 2023-02-03, v3.26.0-rc2~15^2).
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| | |
587c0443cc FindCUDAToolkit: Support CUDA version extraction from version.json
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8451
|
| |
| |
| |
| | |
Fixes: #24858
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
1d6c343661 FindCUDAToolkit: Add missing static library dependencies on pthread and libdl
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8422
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
0e0eb12918 FindCUDAToolkit: Update nvrtc section to clarify a static version exists
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8436
|
| | | |
| | | |
| | | |
| | | | |
Fixes #24798
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
1d6c343661 FindCUDAToolkit: Add missing static library dependencies on pthread and libdl
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8422
|
| | | |
| | | |
| | | |
| | | | |
Discourse-topic: https://discourse.cmake.org/t/7946
|
|\ \ \ \
| |_|/ /
|/| | /
| | |/
| |/|
| | |
| | | |
11a9f88bdf FindCUDAToolkit: Fix nvrtc_static dependencies on Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8405
|
| |/
| |
| |
| |
| |
| | |
Required for CUDA toolkit 11.5:
* https://docs.nvidia.com/cuda/archive/11.5.0/nvrtc/index.html#build-instruction
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
8711231739 FindCUDAToolkit: nvptxcompiler_static correctly specify dependencies
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8395
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
8711231739 FindCUDAToolkit: nvptxcompiler_static correctly specify dependencies
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8395
|
| | |
| | |
| | |
| | | |
Avoids linking to `Threads::Threads` on non-unix systems where it isn't needed. In addition ensures that dlopen symbols are resolved.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
516d807423 FindCUDAToolkit: Add dependency between cusparse and nvJitLink
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8397
|
| |/
| |
| |
| | |
Starting in CUDA 12.0 cusparse uses nvJitLink. As part of verifying this PR I also corrected the nvJitLink dependencies
|
| |
| |
| |
| |
| | |
- CUDAToolkit_BIN_DIR (was already "advanced" sometimes)
- CUDAToolkit_CUPTI_INCLUDE_DIR
|
| |
| |
| |
| | |
Fixes #24575
|
| | |
|
|/
|
|
|
|
|
|
| |
The cuFile API documentation has moved, so link to its new location.
The nvGRAPH library has been removed, so link to a web archive copy.
The NTVX library has a higher-level landing page.
|
|
|
|
|
|
| |
Update the change from commit 2a94c762ed (FindCUDAToolkit: Add support
for CUDA::nvrtc_static, 2023-01-20, v3.26.0-rc1~55^2). The lib is named
`libnvrtc-builtins_static.a`, not `libnvrtc_builtins_static.a`.
|
| |
|
|
|
|
| |
Fixes #24192
|
| |
|
| |
|
|
|
|
| |
Fixes: #24188
|
|\
| |
| |
| |
| |
| |
| |
| | |
989d50d7fc FindCUDAToolkit: Support nvhpc splayed layouts without symlinks
207518b6e8 FindCUDAToolkit: Handle CUDAToolkit_TARGET_DIR dir being a symlink
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7945
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
c7ece269da FindCUDAToolkit: Handle toolkits that don't provide nvptxcompiler
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7932
|
| |
| |
| |
| |
| |
| | |
Some versions of the CUDA toolkit don't provide any static
libraries, and therefore we need to handle that `nvptxcompiler_static`
might not be found
|
|/
|
|
| |
Fixes #24140
|
|
|
|
| |
Fixes #24119
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
01cfd0163d FindCUDAToolkit: Add support for the nvptx compiler library
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7779
|
| |
| |
| |
| | |
Fixes #23892
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
f0918fe505 FindCUDAToolkit: Correctly state cusolver and cublas dependencies
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7633
|
| |
| |
| |
| | |
Fixes #23920
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
1f3c3589f1 FindCUDAToolkit: Search the cuda toolkit include path for cupti
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7608
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
nvtx3 is a header-only replacement for the previous shared library
implementations.
I implemented it as a separate target since while the header names match and
ideally it should be API compatible, forcing its include directory into the old
target would lengthen the include search path and could cause confusion or
possible build differences for projects using multiple build systems. This
keeps it explicit as a developer opt-in.
Implements: #21377
Resolves: #23835
|
|/
|
|
|
|
|
|
| |
CUDA's cupti library has its headers in a seperate directory on a
standard CUDA install, but `CUDA::cupti` only adds the default cuda
include directory.
Issue: #22761
|
|
|
|
| |
Fixes #23347
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 14d8a276 (CUDA: Support nvcc 11.5 new -arch=all|all-major flags,
2021-08-17) added all and all-major options to CUDA_ARCHITECTURES. These are
fairly generic and likely to see real-world use by distributors. Thus it's
desirable to support these also for Clang and older NVCC versions.
The supported architectures are dependent on the toolkit version. We determine
the toolkit version prior to compiler detection. For NVCC we get the version
from the vendor identification output, but for Clang we need to invoke NVCC
separately.
The architecture information is mostly based on the Wikipedia list with the
earliest supported version being CUDA 7.0. This could be documented and
expanded in the future to allow projects to query CUDA toolkit version and
architecture information.
For Clang we additionally constrain based on its support.
Additionally the architecture mismatch detection logic is fixed, improved and
updated for generic support:
* Commit 01428c55 (CUDA: Fail fast if CMAKE_CUDA_ARCHITECTURES doesn't work
during detection, 2020-08-29) enabled CMAKE_CUDA_COMPILER_ID_REQUIRE_SUCCESS
if CMAKE_CUDA_ARCHITECTURES is specified. This results in
CMakeDetermineCompilerID.cmake printing the compiler error and our code for
presenting the mismatch in a user-friendly way being useless. The custom
logic seems preferable so go back to not enabling it.
* Commit 14d8a276 (CUDA: Support nvcc 11.5 new -arch=all|all-major flags,
2021-08-17) tried to support CMP0054 but forgot to add x to the interpolated
result. Thus the conditions would always evaluate to false. This is fixed as
a byproduct of removing NVIDIA specific checks, improving the error message
and replacing architectures_mode with a simpler architectures_explicit.
Visual Studio support omits testing the flags during detection due to
complexities in determining the toolkit version when using it.
A long-term proper implementation would be #23161.
Implements #22860.
|