cuTENSOR Tensor contraction #213
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ryanmrichard
approved these changes
May 14, 2025
Member
Author
|
🚀 [bumpr] Bumped! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
These changes introduce a GPU implementation of the contraction operation using the cuTENSOR library. If the CMake option
ENABLE_CUTENSORis setON(defaults toOFF), the CPU implementation of tensor contraction is switched off in favor of the GPU version. In the long run the switching between CPU and GPU options should be handled more dynamically, but this should suffice for an initial attempt. We also don't have an option to test these changes in GHA at the moment.Note,
ENABLE_CUTENSORis not compatible withENABLE_SIGMA, and will override it toOFFif it is setON.