clarify how to properly use and modify shared OpenCL objects #1243
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
Refer to the OpenCL memory consistency model vs. duplicating requirements.
|
Does this appendix now give any new information? Maybe we should remove it altogether. |
Like the other sections in this appendix I think the remaining text in this section is still informative. Though it is just referring to behaviour described more completely in the main spec. This and the other two sections highlight consequences of this specification (and the C specification) that are relevant to both implementors and users. |
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.
Fixes #1114
Rephrases and simplifies the requirements to properly use and modify shared OpenCL objects.
Refers to the chapter describing the OpenCL memory consistency model vs. duplicating information.