search for: culldist

...*name, unsigned size, > _mesa_glsl_error(&loc, state, "`gl_ClipDistance' array size cannot " > "be larger than gl_MaxClipDistances (%u)", > state->Const.MaxClipPlanes); > + } else if (strcmp("gl_CullDistance", name) == 0 > + && size > state->Const.MaxClipPlanes) { > + /* From the ARB_cull_distance spec: > + * > + * "The gl_CullDistance array is predeclared as unsized and > + * must be sized by the shader either redeclar...

...ias.johannes.klausmann at mni.thm.de> wrote: >> >> On 24.05.2015 20:25, Ilia Mirkin wrote: >>> I'm having a bit of trouble tracing through this. What happens if I >>> have a shader that just does: >>> >>> gl_ClipDistance[0] = 1; >>> gl_CullDistance[0] = 1; >>> >>> what does the resulting TGSI look like? (Assuming that clip plane 0 is >>> enabled.) What about the generated nvc0 code (for the vertex shader)? >> >> (hack up a patch for this, run it without DRI_PRIME=1, see i pass and forget >> to...

...ance mesa/main: add support for GL_ARB_cull_distance mesa/prog: Add varyings for arb_cull_distance mesa/st: add support for GL_ARB_cull_distance glsl: Add a helper to see if an array was unsize in the shader glsl: Add arb_cull_distance support i965: rename UsesClipDistanceOut to UsesClipCullDistanceOut gallium: add support for arb_cull_distance nouveau/codegen: sort in galliums cull_distance semantic into the drivers bitmask nouveau/nvc0: implement cull_distance as a special form of clip distance docs/GL3.txt | 2 +- docs/relnotes/10....

On 24.05.2015 20:25, Ilia Mirkin wrote: > I'm having a bit of trouble tracing through this. What happens if I > have a shader that just does: > > gl_ClipDistance[0] = 1; > gl_CullDistance[0] = 1; > > what does the resulting TGSI look like? (Assuming that clip plane 0 is > enabled.) What about the generated nvc0 code (for the vertex shader)? (hack up a patch for this, run it without DRI_PRIME=1, see i pass and forget to check it again) yeah those are equal, sorry for w...

...5 at 9:40 AM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > > On 25.05.2015 07:17, Dave Airlie wrote: >> >> On 25 May 2015 at 08:11, Marek Olšák <maraeo at gmail.com> wrote: >>> >>> It's the same on Radeon. There are 2x ClipOrCullDistance output >>> vectors and a mask saying it should clip or cull or do nothing. >>> >>> Marek >>> >> My thinking was gallium should have a single semantic and a mask in >> the shader definition maybe. >> >> though it doesn't solve the d...