Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] SASS disassembly always tries to use nvdisasm on the PATH #9

Open
gmarkall opened this issue Jul 4, 2024 · 1 comment · May be fixed by #13
Open

[BUG] SASS disassembly always tries to use nvdisasm on the PATH #9

gmarkall opened this issue Jul 4, 2024 · 1 comment · May be fixed by #13
Labels
bug Something isn't working

Comments

@gmarkall
Copy link
Collaborator

gmarkall commented Jul 4, 2024

See:

numba-cuda/numba_cuda/numba/cuda/codegen.py

Lines 27 to 29 in e3658d4

cp = subprocess.run(['nvdisasm', *flags, fname], check=True,
stdout=subprocess.PIPE,
stderr=subprocess.PIPE)

It would be better to search for CUDA command line tools in the more normal way, e.g. from CUDA_HOME / CUDA_PATH first.
@gmarkall gmarkall added the bug Something isn't working label Jul 4, 2024
@brycelelbach
Copy link
Contributor

It'd probably make sense to add logic for the search in cuda_paths.py alongside the nvvm and libdevice searches.

https://github.com/NVIDIA/numba-cuda/blob/main/numba_cuda/numba/cuda/cuda_paths.py

brycelelbach added a commit to brycelelbach/numba-cuda that referenced this issue Jul 5, 2024
@brycelelbach
Search for nvdisasm in the conda environment / CUDA_HOME / default …
7abcd36 
…CUDA install

location in addition to the path. Fixes NVIDIA#9.
@brycelelbach brycelelbach linked a pull request Jul 5, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
2 participants
@brycelelbach @gmarkall