JuliaGPU/CUDA.jl

Naming inconsistencies in generic dense cuSOLVER functions

Open

#3,085 opened on Apr 9, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Julia (274 forks)batch import
good first issue

Repository metrics

Stars
 (1,408 stars)
PR merge metrics
 (Avg merge 5d 5h) (16 merged PRs in 30d)

Description

Describe the bug

There are some naming inconsistencies in the generic dense cuSOLVER API, where some Xroutine functions are wrapped instead as routine.

Xsytrs

https://github.com/JuliaGPU/CUDA.jl/blob/a9a687cf541c1cdc91e0b6884382f6fd57ceb417/lib/cusolver/src/dense_generic.jl#L125 https://github.com/JuliaGPU/CUDA.jl/blob/a9a687cf541c1cdc91e0b6884382f6fd57ceb417/lib/cusolver/src/dense_generic.jl#L152

Xtrtri

https://github.com/JuliaGPU/CUDA.jl/blob/a9a687cf541c1cdc91e0b6884382f6fd57ceb417/lib/cusolver/src/dense_generic.jl#L180

Xlarft

https://github.com/JuliaGPU/CUDA.jl/blob/a9a687cf541c1cdc91e0b6884382f6fd57ceb417/lib/cusolver/src/dense_generic.jl#L205

Contributor guide

Research direction
Inspect the referenced lines and rename the functions to follow the cuSOLVER naming convention (e.g., Xsytrs to sytrs).
Tech stack
None
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJulia
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75