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.

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

Use cuda.bindings and cuda.core for Linker #133

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

brandon-b-miller
Copy link
Collaborator

WIP
xref #129

@leofang
Copy link
Member

leofang commented Feb 22, 2025

Thanks, @brandon-b-miller. Remember our goal is to drop every Linker subclasses inside Numba, in favor of cuda.core.Linker. The current PR is not what we want. Also note that to help pynvjitlink to phase out, we already have rapidsai/pynvjitlink#111 which is essentially what this PR does today.

@brandon-b-miller brandon-b-miller changed the title Use cuda.bindings and cuda.core for nvjitlink Use cuda.bindings and cuda.core for Linker Feb 24, 2025
Copy link

copy-pr-bot bot commented Feb 24, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.


# Load
cufunc = module.get_function(self._entry_name)
#cufunc = module.get_function(self._entry_name)
cufunc = cubin.get_kernel(self._entry_name)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we switched to context independent loading API, the CUDADispatcher.bind method should probably be renamed since it no longer binds context via calling the get_cufunc function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants