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

Add HIP backend #242

Closed
loostrum opened this issue Nov 30, 2023 · 0 comments · Fixed by #289
Closed

Add HIP backend #242

loostrum opened this issue Nov 30, 2023 · 0 comments · Fixed by #289
Labels
enhancement New feature or request

Comments

@loostrum
Copy link
Member

Currently cudawrappers (obviously) only support CUDA. The suggestion is split the user interface from the backend, so we could have a CUDA backend as we currently do and add a HIP backend. This way, the user could write that could run either with CUDA directly, CUDA through HIP, or on AMD GPUs through HIP.

As a potential use case, I have a proof-of-concept tensor-core based beamformer currently written in both CUDA and HIP, which runs in all three ways described above. As the HIP and CUDA commands are basically identical apart from the prefix, this results in a lot of duplicated code that could be hidden very nicely by cudawrappers. Potential followup issue: come up with a new name for cudawrappers as it would no longer be cuda-only.

@loostrum loostrum added the enhancement New feature or request label Nov 30, 2023
@loostrum loostrum linked a pull request Jul 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant