Clarify HLSL to GLSL comparison for compute shader barriers#354
Merged
spencer-lunarg merged 1 commit intoKhronosGroup:mainfrom Mar 3, 2026
Merged
Clarify HLSL to GLSL comparison for compute shader barriers#354spencer-lunarg merged 1 commit intoKhronosGroup:mainfrom
spencer-lunarg merged 1 commit intoKhronosGroup:mainfrom
Conversation
Contributor
Author
|
@SaschaWillems Could you kindly make a review? |
Collaborator
|
Sorry for the late reply, but my knowledge in that area is a bit limited, so I can't really review this. |
spencer-lunarg
approved these changes
Mar 3, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Want to clarify compute shaders barriers. To do this, I compared the language mappings to SPIR-V: