GLSL: Fix bug setting component=0 for an auto-location assignment.
Setting component=0 is later taken to mean the shader did so, which is not always legal. It should instead set the component as not set by the shader.
This commit is contained in:
parent
8de7e7bf14
commit
94c18a84cd
7 changed files with 21 additions and 22 deletions
|
|
@ -47,12 +47,10 @@ Warning, version 450 is not yet complete; most version-specific features are pre
|
|||
Decorate 19(singleBlock) Location 2
|
||||
MemberDecorate 20(bn) 0 Patch
|
||||
MemberDecorate 20(bn) 0 Location 20
|
||||
MemberDecorate 20(bn) 0 Component 0
|
||||
MemberDecorate 20(bn) 1 Patch
|
||||
MemberDecorate 20(bn) 1 Location 24
|
||||
MemberDecorate 20(bn) 2 Patch
|
||||
MemberDecorate 20(bn) 2 Location 25
|
||||
MemberDecorate 20(bn) 2 Component 0
|
||||
Decorate 20(bn) Block
|
||||
2: TypeVoid
|
||||
3: TypeFunction 2
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue