You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEA]: Support for finding binary utilities like nvdisasm #762
Is your feature request related to a problem? Please describe.
(Marked "not sure" for the area because there's no pathfinder choice)
In Numba-CUDA we have NVIDIA/numba-cuda#13 which attempts to improve the logic for finding nvdisasm. However, as we're leaning on pathfinder for all the path-finding logic now, it'd be nice to also be able to locate nvdisasm and other tools with pathfinder. Is this something that's planned / in-scope?
to get the paths of the best choice for running these utilities.
Describe alternatives you've considered
Continuing to attempt to locate nvdisasm in Numba-CUDA. This is OK to do, but I wonder if this is a common need - I think I have seen people asking about doing similar things for other libraries / purposes when they need to produce SASS for user inspection.
changed the title [-][FEA]: Support for finding utilities like `nvdisasm`[/-][+][FEA]: Support for finding binary utilities like `nvdisasm`[/+]on Sep 26, 2025
This doesn't seem like it's on the critical path of #1036 anymore. There are no uses of nvdiasm or cuobjdump in numba-cuda AFAICT from rg-ing around the repo.
Activity
[-][FEA]: Support for finding utilities like `nvdisasm`[/-][+][FEA]: Support for finding binary utilities like `nvdisasm`[/+]pathfinderusable as a full replacement forcuda_paths.pyinnumba-cuda#1036cpcloud commentedon Feb 2, 2026
This doesn't seem like it's on the critical path of #1036 anymore. There are no uses of
nvdiasmorcuobjdumpinnumba-cudaAFAICT fromrg-ing around the repo.cpcloud commentedon Feb 2, 2026
Correction:
cuobjdumpis still there, myrgpattern was off by 1 :)gmarkall commentedon Feb 4, 2026
I see uses of
nvdisasm(and I believe it is used if you callk.inspect_sass()for any kernelk. Were you grepping fornvdiasm?