-
Notifications
You must be signed in to change notification settings - Fork 30
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
EXSWHTEC-75 - Implement tests for hipMemcpyAsync and derivatives #18
EXSWHTEC-75 - Implement tests for hipMemcpyAsync and derivatives #18
Conversation
Change-Id: I66f0c09e9c7405ec7430b1883e0e89542fdb87a0
Change-Id: I212b82b1b3a78a368b85ea64e338371a34b405f9
Change-Id: Ib455f72b5be77e1a81137d15c07ea41161b16a3e
Change-Id: Ief96e274f4143e80ceb3e40f04d38ae217777583
Change-Id: I9c03cde09b42c8e3726153c2a177359efc8d6d29
- Basic positive tests - Negative parameter tests
…hipMemcpyAsync_tests
@milos-mozetic / @music-dino : Can someone look into this PR. The previous resolution of the merge conflict 1ef552a looks incorrect. There are some remnants of the merge conflict that can be seen in hipMemcpyAsync.cc. |
@mangupta: Sorry for the inconvenience, now the conflict is resolved appropriately within commit dc236b8. @music-dino: can you please double-check that the content of hipMemcpyAsync.cc is as expected from your side? |
Any update? |
The contents seem to be correct. Please proceed with the merge. |
@music-dino |
Merge conflicts have been resolved, please proceed. |
Implement positive and negative unit tests for the following APIs:
hipMemcpyAsync
hipMemcpyDtoHAsync
hipMemcpyHtoDAsync
hipMemcpyDtoDAsync.