Clarify setting work_dim to zero in command-buffer update
#1395
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
Actions Issue KhronosGroup#1390 by clarifying that `work_dim` can be set to zero to signify no change to the kernle command work dimensions. This is the behavior currently expected in the CTS tests.
EwanC
changed the title
work_dim to zero in command-buffer updatework_dim to zero in command-buffer update
|
Merging as discussed in the July 1st teleconference. |
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.
Progresses Issue #1390 by clarifying that
work_dimcan be set to zero to signify no change to the kernle command work dimensions. This is the behavior currently expected in the CTS tests.Note I have a comment in that issue about further changes we may want to make #1390 (comment)