search for: clipdist

...n a shader_test for this a while ago which you pushed to piglit > (fs-cull-and-clip-distance-different.shader_test). If i remember right > nvidia passed that test just fine. My take (and note that I last read the extension many months ago) is that you're supposed to figure out the max gl_ClipDistance[] written, and then write all your cull distances above that. So if you, e.g., have something like gl_ClipDistance[5] = 1; gl_CullDistance[0] = 1; Then it would decide that there are 6 clip distances (or if there's an explicit out float gl_ClipDistance[n], then use that), and 1 cull dista...

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

...nvidia passed that test just fine. Ah btw, if we follow Brian Paul, overlapping indexes are fine! (and it is way more intuitive to use for a shader developer) >> My take (and note that I last read the extension many months ago) is >> that you're supposed to figure out the max gl_ClipDistance[] written, >> and then write all your cull distances above that. So if you, e.g., >> have something like >> >> gl_ClipDistance[5] = 1; >> gl_CullDistance[0] = 1; >> >> Then it would decide that there are 6 clip distances (or if there's an >> e...

...:30 PM, Tobias Klausmann > <tobias.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=...

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...

...ase; + base.oldBase = info.first; + base.newBase = tempBase; + indirectTempBases.insert(std::make_pair(*it, base)); + tempBase += info.second; + } + info->bin.tlsSpace += tempBase * 16; + } if (info->io.genUserClip > 0) { info->io.clipDistances = info->io.genUserClip; @@ -1208,6 +1223,9 @@ bool Source::scanDeclaration(const struct tgsi_full_declaration *decl) case TGSI_FILE_TEMPORARY: for (i = first; i <= last; ++i) tempArrayId[i] = arrayId; + if (arrayId) + tempArrayInfo.insert(std::make_pair(...

...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 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...