Is this a duplicate?
Area
cuda.pathfinder
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?
Describe the solution you'd like
Something like
nvdisasm_path = cuda.pathfinder.binary_utility('nvdisasm')
cuobjdump_path = cuda.pathfinder.binary_utility('cuobjdump')
# ... etc ...
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.
Additional context
No response
Is this a duplicate?
Area
cuda.pathfinder
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 onpathfinderfor all the path-finding logic now, it'd be nice to also be able to locatenvdisasmand other tools withpathfinder. Is this something that's planned / in-scope?Describe the solution you'd like
Something like
to get the paths of the best choice for running these utilities.
Describe alternatives you've considered
Continuing to attempt to locate
nvdisasmin 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.Additional context
No response