First steps to enable SYCL backend in Python Interface #155
Conversation
This file contains 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
Signed-off-by: Lukas Sommer <[email protected]>
Signed-off-by: Lukas Sommer <[email protected]>
Signed-off-by: Lukas Sommer <[email protected]>
Signed-off-by: Lukas Sommer <[email protected]>
Signed-off-by: Lukas Sommer <[email protected]>
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.
First implementation steps towards supporting the SYCL backend in the CUTLASS Python Interface.
The two main additions from this PR are:
nvccto compile device and host code.The support is not complete yet, i.e., it is not yet possible to launch a kernel. Notable missing components include data transfer handling via SYCL and kernel launch.
Compilation is currently only possible with development versions of DPC++, the
-fsycl-rtc-modeflag that was added to support CUTLASS nested parameter classes in free-function kernels as part of this work is not yet available in releases.The activation of the SYCL backend via environment variable is a temporary solution, a follow-up will look into a cleaner solution.