Avoid incorrect flag when create ocl memory object. #181
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
If there is already a CL_MEM_USE_HOST_PTR, we should not add CL_MEM_COPY_HOST_PTR. According to the OpenCL spec: " CL_MEM_COPY_HOST_PTR and CL_MEM_USE_HOST_PTR are mutually exclusive. " Signed-off-by: Zhigang Gong <[email protected]>
|
Thanks for your contribution! |
karlrupp
added a commit
that referenced
this pull request
Mar 3, 2016
OpenCL: Avoid incorrect flag when create ocl memory object.
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.
If there is already a CL_MEM_USE_HOST_PTR, we should not
add CL_MEM_COPY_HOST_PTR. According to the OpenCL spec:
"
CL_MEM_COPY_HOST_PTR and
CL_MEM_USE_HOST_PTR are mutually exclusive.
"
Signed-off-by: Zhigang Gong [email protected]