Warnings in the CUDA backend
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start with resolve/LinSolverDirectCuSparseILU0.hpp and resolve/LinSolverDirectCuSolverRf.cpp, then build the CUDA backend with the reported CUDA 12.9 environment to reproduce the warnings. Trace the deprecated csrilu02Info_t and cuSolver calls, and define completion as an agreed supported replacement or documented compatibility path with the warnings addressed.
Written by the indexing model from the issue text.
Description
I noticed some warnings in the CUDA backend while testing #371. Deprecated features that may be removed in future CUDA versions.
A first set of warning pertains to csrilu02Info_t
In file included from /home/97k/ReSolve/tests/functionality/testRandGmres.cpp:27:
/home/97k/ReSolve/resolve/LinSolverDirectCuSparseILU0.hpp:65:40: warning: ‘csrilu02Info_t’ is deprecated: The type will be removed in the next major release [-Wdeprecated-declarations]
65 | csrilu02Info_t info_A_{nullptr};
| ^
In file included from /usr/local/cuda/include/cusolverSp.h:53,
from /home/97k/ReSolve/resolve/workspace/LinAlgWorkspaceCUDA.hpp:4,
from /home/97k/ReSolve/resolve/workspace/LinAlgWorkspace.hpp:6,
from /home/97k/ReSolve/tests/functionality/testRandGmres.cpp:24:
/usr/local/cuda/include/cusparse.h:238:22: note: declared here
238 | struct csrilu02Info* csrilu02Info_t CUSPARSE_DEPRECATED_TYPE;
| ^~~~~~~~~~~~~~
Another set of warnings pertains to cuSolver calls. We have found cuDSS to be less performant that cuSolver, but we will eventually need to address this if the feature is removed. E.g.,
/home/97k/ReSolve/resolve/LinSolverDirectCuSolverRf.cpp: In member function ‘virtual int ReSolve::LinSolverDirectCuSolverRf::setup(ReSolve::matrix::Sparse*, ReSolve::matrix::Sparse*, ReSolve::matrix::Sparse*, ReSolve::index_type*, ReSolve::index_type*, ReSolve::LinSolverDirectCuSolverRf::vector_type*)’:
/home/97k/ReSolve/resolve/LinSolverDirectCuSolverRf.cpp:135:47: warning: ‘cusolverStatus_t cusolverRfSetupDevice(int, int, int*, int*, double*, int, int*, int*, double*, int, int*, int*, double*, int*, int*, cusolverRfHandle_t)’ is deprecated: please use cuDSS instead [-Wdeprecated-declarations]
Build environment:
- pdesx system
- CUDA 12.9
- gcc 11.4.0
- Dominant language
- C++
- Stars
- 85
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ORNL/ReSolve
-
SystemSolver still uses string to select configuration optionsMay be free again A pull request for this issue was closed without being merged. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Support unpreconditioned GMRESMay be free again @kakeueda claimed this 47 days ago, and no pull request is open. Openenhancement iterative solver
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Support P and Q permutations provided by the user in `LinSolverDirectKLU`May be free again @stark256-spec claimed this 39 days ago, and no pull request is open. Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
useless statementOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
grizzlypeak3d/DJV#962 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day