We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In https://embarkstudios.github.io/rust-gpu/api/spirv_std/arch/fn.control_barrier.html , there's no explanation of the MEMORY template parameter, or even what values are valid in it. (Turns out it is a scope, just like the EXECUTION parameter).
I guess what would be most immediately helpful is basically just examples matching the common ones like HLSL's GroupMemoryBarrierWithGroupSync.
The text was updated successfully, but these errors were encountered:
Here's an exact implementation of GroupMemoryBarrierWithGroupSync(), verified against the output of DXC:
unsafe { control_barrier::< { Scope::Workgroup as u32 }, { Scope::Workgroup as u32 }, { Semantics::WORKGROUP_MEMORY.bits() | Semantics::ACQUIRE_RELEASE.bits() }, >(); }
Maybe we should have a library of wrappers for common combinations.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
In https://embarkstudios.github.io/rust-gpu/api/spirv_std/arch/fn.control_barrier.html , there's no explanation of the MEMORY template parameter, or even what values are valid in it. (Turns out it is a scope, just like the EXECUTION parameter).
I guess what would be most immediately helpful is basically just examples matching the common ones like HLSL's GroupMemoryBarrierWithGroupSync.
The text was updated successfully, but these errors were encountered: