[SYCL][COMPAT] Adding 2-byte and 4-bytes memset operations to headers #13409
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
AidanBeltonS
approved these changes
Apr 16, 2024
|
@intel/llvm-gatekeepers This is ready for merging Thanks! CUDA backend failure unrelated. Issue already reported. |
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.
This PR replaces #11340
This PR extends the memory header to include 2 byte and 4 byte memsets.
sycl::fill. Functionality remains unchanged as it is exposed throughdetail::memset<unsigned char>, equivalent to what we had before.sycl::fillusing 2-byte and 4-byte datatypesAdded tests for memset_d16 and memset_d32.