Add missing opencl-arrayfire interop fns in unified backend #2981
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
API that is required for users to use OpenCL and ArrayFire simultaneously in their application were missing from unified backend. CUDA doesn't have this issue. Somehow, OpenCL wasn't added earlier and this change fixes that problem
Changes to Users
Users using unified backend will also be able to use Raw OpenCL and ArrayFire simultaneously. Earlier, they could do this only by directly using the OpenCL backend.
Checklist
[ ] Tests pass[ ] Functions added to unified API[ ] Functions documented