![]() ![]() Make: *** Deleting file 'utils/HAMR/CMakeFiles/hamr.dir/sm_80. opt/nvidia/hpc_sdk/Linux_x86_64/22.7/cuda/11.7/bin/nvlink -arch=sm_80 -register-link-binaries=utils/HAMR/CMakeFiles/hamr.dir/cmake_cuda_register.h -o=utils/HAMR/CMakeFiles/hamr.dir/sm_80.cubin utils/HAMR/CMakeFiles/hamr.dir/hamr_openmp_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_copy_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_malloc_host_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_malloc_async_ utils/HAMR/CMakeFiles/hamr.dir/hamr_openmp_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_malloc_ utils/HAMR/CMakeFiles/hamr.dir/hamr_ utils/HAMR/CMakeFiles/hamr.dir/hamr_malloc_ utils/HAMR/CMakeFiles/hamr.dir/hamr_new_ utils/HAMR/CMakeFiles/hamr.dir/hamr_openmp_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_malloc_uva_ utils/HAMR/CMakeFiles/hamr.dir/hamr_cuda_ utils/HAMR/CMakeFiles/hamr.dir/hamr_host_ utils/HAMR/CMakeFiles/hamr.dir/hamr_ utils/HAMR/CMakeFiles/hamr.dir/hamr_ utils/HAMR/CMakeFiles/hamr.dir/hamr_openmp_ utils/HAMR/CMakeFiles/hamr.dir/hamr_buffer_ /opt/nvidia/hpc_sdk/Linux_x86_64/22.7/cuda/11.7/lib64/libcudart.so Make -f utils/HAMR/CMakeFiles/hamr.dir/build.make utils/HAMR/CMakeFiles/hamr.dir/build Suggested build types are values such as Debug and Release, but CMake allows any type that is supported by the build tool. Make: Leaving directory '/pscratch/sd/l/loring/sensei-build-clang_cuda_omp' Summary Postscript A Simple Build Script Configuring Debug and Release Builds CMake refers to different build configurations as a Build Type. Make: Entering directory '/pscratch/sd/l/loring/sensei-build-clang_cuda_omp'Ĭd /pscratch/sd/l/loring/sensei-build-clang_cuda_omp & /global/common/software/nersc/pm-2021q4/sw/cmake-3.22.0/bin/cmake -E cmake_depends "Unix Makefiles" /pscratch/sd/l/loring/SENSEI /pscratch/sd/l/loring/SENSEI/utils/HAMR /pscratch/sd/l/loring/sensei-build-clang_cuda_omp /pscratch/sd/l/loring/sensei-build-clang_cuda_omp/utils/HAMR /pscratch/sd/l/loring/sensei-build-clang_cuda_omp/utils/HAMR/CMakeFiles/hamr.dir/DependInfo.cmake -color= Make -f utils/HAMR/CMakeFiles/hamr.dir/build.make utils/HAMR/CMakeFiles/hamr.dir/depend Here is the output when I run make: $make VERBOSE=1 In any case, does any one have advice on how to tell CMake not to use nvlink when clang is the cuda compiler and instead use clang? ![]() Clang devs will likely test linking with clang but they may not test linking w. This seems to me potentially risky choice and creates the potential for some unnecessary complications since clang itself can be the linker. Cmake is using nvlink for device linking step even when clang is the cuda compiler. recent versions of clang, including mainline nightly build, my project build fails due to a segv when device linking. RobertCrovella June 2, 2019, 10:37am 4 CMake went through a significant change in how it dealt with CUDA in the 3.8 - 3.12 timeframe. As the title says, I’m using clang as both C++ and CUDA compiler. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |