search for: actual_clip_writes_mask

...ll distance. In the TGSI, I'm thinking this might look approximately like PROPERTY CULL_MASK (1<<6) DCL OUT[0], CLIPDIST[0] DCL OUT[1], CLIPDIST[1] MOV OUT[1].y, 1 (clip distance[5]) MOV OUT[1].z, 1 (cull distance[0]) Then basically you'd have (rast->clip_enable & shader->actual_clip_writes_mask) | cull_mask = the enabled distances cull_mask = cull mask This would work *very* well for nouveau, not sure how suitable it is for other hardware. Cheers, -ilia

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

...>> PROPERTY CULL_MASK (1<<6) >> DCL OUT[0], CLIPDIST[0] >> DCL OUT[1], CLIPDIST[1] >> MOV OUT[1].y, 1 (clip distance[5]) >> MOV OUT[1].z, 1 (cull distance[0]) >> >> Then basically you'd have >> >> (rast->clip_enable & shader->actual_clip_writes_mask) | cull_mask = >> the enabled distances >> cull_mask = cull mask >> >> This would work *very* well for nouveau, not sure how suitable it is >> for other hardware. >> >> Cheers, >> >> -ilia