We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rayuela.jl/deps/build.jl
Lines 58 to 59 in a3a1bed
While looking at https://discourse.julialang.org/t/freeing-memory-in-the-gpu-with-cudadrv-cudanative-cuarrays/10946, I ran into issues building the package because you can't assume nvcc lives there and you might need to pass -ccbin options. CUDAapi does that for you, see eg. https://github.com/JuliaGPU/CUDAnative.jl/blob/1833651e180fa71157a31f0b6d2588a0ad338c7e/test/perf/launch_overhead/build.jl
nvcc
-ccbin
Same with the arch_ options, better figure that out accurately by looking at CUDAdrv, for maximal compatibility with user GPUs.
arch_
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Rayuela.jl/deps/build.jl
Lines 58 to 59 in a3a1bed
While looking at https://discourse.julialang.org/t/freeing-memory-in-the-gpu-with-cudadrv-cudanative-cuarrays/10946, I ran into issues building the package because you can't assume
nvcc
lives there and you might need to pass-ccbin
options. CUDAapi does that for you, see eg. https://github.com/JuliaGPU/CUDAnative.jl/blob/1833651e180fa71157a31f0b6d2588a0ad338c7e/test/perf/launch_overhead/build.jlSame with the
arch_
options, better figure that out accurately by looking at CUDAdrv, for maximal compatibility with user GPUs.The text was updated successfully, but these errors were encountered: