search for: arb_cull_dist

...;> This patch series adds the needed support for this extension to the various >> parts of mesa to finally enable it for nvc0. >> >> Dave Airlie (1): >> glsl: lower cull_distance into cull_distance_mesa >> >> Tobias Klausmann (10): >> glapi: add GL_ARB_cull_distance >> 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 supp...

..."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 redeclaring it with > + * a size or indexing it only with integral constant > + * expressions. The size determines the...

...gt;>>> various >>>> parts of mesa to finally enable it for nvc0. >>>> >>>> Dave Airlie (1): >>>> glsl: lower cull_distance into cull_distance_mesa >>>> >>>> Tobias Klausmann (10): >>>> glapi: add GL_ARB_cull_distance >>>> 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 >>...

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 does nvidia do the right thing with

On 27.05.2015 18:28, Marek Olšák wrote: > Another thing to consider is linking shaders that occur before the > rasterizer (e.g. any two shaders from VS->TCS->TES->GS). The maximum > number of written distances is still 8, but what happens if VS writes > 1x clip and 7x cull and GS reads 8x clip and no cull? i think this should be rejected anyway (in the glsl?!), constraining

This patch series adds the needed support for this extension to the various parts of mesa to finally enable it for nvc0. Dave Airlie (1): glsl: lower cull_distance into cull_distance_mesa Tobias Klausmann (10): glapi: add GL_ARB_cull_distance 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 UsesClip...

On Mon, May 25, 2015 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