[Mesa-dev] [PATCH 0/2 v2] Add support for clip distances in Gallium
jfonseca at vmware.com
Tue Dec 13 12:11:20 PST 2011
----- Original Message -----
> This is an updated version of the patch set I sent to the list a few
> There is now a TGSI property called
> that drivers can use to determine how many of the 8 available clip
> are actually used by a shader.
Can't the info in TGSI_PROPERTY_NUM_CLIP_DISTANCES be easily derived from the shader, and queried through src/gallium/auxiliary/tgsi/tgsi_scan.h ?
Could you also elaborate on why TGSI_SEMANTIC_CLIPDIST is useful for the drivers? I personally don't have nothing against it, but just like to understand why it makes a difference.
More information about the mesa-dev