-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
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
Incorrect colVal array when using CuSparseMatrixCSR command on sparse matrix #1888
Comments
Which version of CUDA.jl? cc @amontoison |
CUDA.versioninfo() |
Tim, is CUDA toolkit 12.1.1 used by default now? |
The command Pkg.status("CUDA"), gives out the following: |
@HamMoh94 pkg> add CUDA#master |
@amontoison The issue is resolved after adding the branch master. |
Great! I'm using CUDA |
The command CuSparseMatrixCSR incorrectly generates the colVal inner array when applying it on a sparse matrix of form CSC with a specific size. This can be easily seen by generating a sparse identity matrix (A) of size (N,N) and then loading it on GPU using the command CuSparseMatrixCSR(A). We expect the colVal array to be (1:1:N). However, the first value is shifted to the last column. More interestingly, the problem showed only for matrices of size (16,32,64,128 ...), but it does not show for other sizes.
The Minimal Working Example (MWE) for this bug:
Expected behavior
We expect to get Acsr.colVal = 1:1:8 But I am getting Acsr.colVal = [8; 1:1:7], while the same applies for the other matrices.
Version info
Details on Julia:
Julia Version 1.8.3
Commit 0434deb161e (2022-11-14 20:14 UTC)
Platform Info:
OS: Linux (x86_64-linux-gnu)
CPU: 128 × AMD EPYC 7542 32-Core Processor
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-13.0.1 (ORCJIT, znver2)
Threads: 1 on 128 virtual cores
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS = ```
Details on CUDA:
CUDA runtime 12.1, artifact installation
CUDA driver 12.1
NVIDIA driver 470.161.3, originally for CUDA 11.4
Libraries:
Toolchain:
1 device:
0: NVIDIA A100 80GB PCIe (sm_80, 59.855 GiB / 79.096 GiB available)
The text was updated successfully, but these errors were encountered: