Repository navigation
[ENH]: Use Driver version to target compatible .so/.dll versions #654
Copy link
Copy link
Open
Labels
cuda.pathfinderEverything related to the cuda.pathfinder moduleEverything related to the cuda.pathfinder moduleenhancementAny code-related improvementsAny code-related improvements
Milestone
Description
Activity
- added a parent issue
on May 22, 2025 - addedenhancementAny code-related improvementsAny code-related improvementsP0High priority - Must do!High priority - Must do!cuda.bindingsEverything related to the cuda.bindings moduleEverything related to the cuda.bindings module
on May 22, 2025 - addedcuda.pathfinderEverything related to the cuda.pathfinder moduleEverything related to the cuda.pathfinder module
on Jul 2, 2025 - changed the title
[-]path_finder enhancement: Use Driver version to target compatible .so/.dll versions[/-][+]pathfinder enhancement: Use Driver version to target compatible .so/.dll versions[/+]on Aug 19, 2025 - removed a parent issue
on Sep 27, 2025 - added a parent issue
on Sep 27, 2025 - changed the title
[-]pathfinder enhancement: Use Driver version to target compatible .so/.dll versions[/-][+][ENH]: Use Driver version to target compatible .so/.dll versions[/+]on Mar 4, 2026 - addedP2Low priority - Nice to haveLow priority - Nice to haveand removedP0High priority - Must do!High priority - Must do!
on Mar 4, 2026 I'm revamping the prioritization for all pathfinder issues.
We have a 2-fold problem here:
- For CUDA libraries that are shipped with CTK:
- Using the driver version to constrain the search is enough
- For CUDA libraries that are shipped outside of CTK (I call them satellite libraries):
- We need a constraint either provided by the user or auto-detection, to express that "I want to load the cuTENSOR build for CUDA 12 not CUDA 13"
- We also need to prepare for satellite libraries that have released multiple major versions. cuTENSOR is also one such example (the 1.x -> 2.x transition was a bit painful) and I don't think the pathfinder is equipped to address this today.
- For CUDA libraries that are shipped with CTK:
- addedP0High priority - Must do!High priority - Must do!and removedcuda.bindingsEverything related to the cuda.bindings moduleEverything related to the cuda.bindings module
on Mar 12, 2026 This is probably best handled under #1038
Metadata
Metadata
Assignees
Labels
cuda.pathfinderEverything related to the cuda.pathfinder moduleEverything related to the cuda.pathfinder moduleenhancementAny code-related improvementsAny code-related improvements
Type
Projects
- StatusShow more project fieldsTodo
This will make a difference in environments with a heterogenous mix of installed CTK libraries.
Closely related discussions: #839