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
Presently pynvjitlink patches and tests against Numba with its builtin CUDA target. The current release of numba-cuda incorporates the pynvjitlink patch so that patching is no longer required.
pynvjitlink should be updated so that:
If numba-cuda is in use, then it does not patch its linker.
If numba-cuda is in use, then it is at least version 0.0.18 (earlier versions don't include the patch, and may not be compatible with being patched by pynvjitlink).
Can you clarify this issue? It seems like there's some conflict between point 1 and point 2.
I think I understand this more now. You meant that if numba-cuda is in use, pynvjitlink should not apply the patch to numba linker. Because after 0.0.18, the patch is already included. And before 0.0.18, pynvjitlink is no longer compatible.
Presently pynvjitlink patches and tests against Numba with its builtin CUDA target. The current release of numba-cuda incorporates the pynvjitlink patch so that patching is no longer required.
pynvjitlink should be updated so that:
This will also allow the Numba-related tests in the pynvjitlink CI to pass with later CUDA toolkits (e.g. 12.5) as it has fixed the expected PTX patterns generated by newer toolkits in the tests of atomics (See https://github.com/NVIDIA/numba-cuda/pull/40/files#diff-d48759455e529fd3994f3380640329c652dae73f5360cb977359c8c43461925b).
The text was updated successfully, but these errors were encountered: