You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be related to the previous interface block issue at #430 (thanks for the prompt fix by the way). I'm now getting namespace collisions between interface blocks, their field names, and other shader inputs and outputs. Finding a minimal program to reproduce the bug is a bit tricky, since name assignments seem unpredictable, but this program
uniform U {vec4 v;};
outvec4 a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v;
gives me the following output (with --format indented):
My video driver won't accept it because the name "U" is reused three times at global scope. In another instance, I had it fail because an interface block name (uniform U in my first code listing) matched a shader output, so they appear to share the same namespace too.
The text was updated successfully, but these errors were encountered:
This might be related to the previous interface block issue at #430 (thanks for the prompt fix by the way). I'm now getting namespace collisions between interface blocks, their field names, and other shader inputs and outputs. Finding a minimal program to reproduce the bug is a bit tricky, since name assignments seem unpredictable, but this program
gives me the following output (with
--format indented
):My video driver won't accept it because the name "U" is reused three times at global scope. In another instance, I had it fail because an interface block name (
uniform U
in my first code listing) matched a shader output, so they appear to share the same namespace too.The text was updated successfully, but these errors were encountered: