KhronosGroup / KhronosGroup/Vulkan-Docs
[Specification] Component Assignment clarification
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
Section 14.1.4. (Location Assignment) of the Vulkan spec says:
"Any two inputs listed as operands on the same OpEntryPoint must not be assigned the same location, either explicitly or implicitly. Any two outputs listed as operands on the same OpEntryPoint must not be assigned the same location, either explicitly or implicitly."
This would appear to suggest that a location cannot be shared even when we have no component aliasing, which would defeat the purpose of supporting the component decorations.
The GLSL spec has the wording "location aliasing is allowed only if it does not cause component aliasing", perhaps the Vulkan spec could be reworded in a similar way?
Contributor guide
Assessment
This issue has not been assessed yet.