llvmpipe: avoid generating tri_16 for tris which extend past tile bounds
authorKeith Whitwell <keithw@vmware.com>
Tue, 2 Nov 2010 14:20:20 +0000 (14:20 +0000)
committerKeith Whitwell <keithw@vmware.com>
Tue, 2 Nov 2010 16:48:10 +0000 (16:48 +0000)
commit98445b43071414a6bd82d0618002611c6ad70257
tree09ce797ac92e5b5001fdd0e3ef5a5f71d2b2e276
parentfc70c05dbd5af94b04cf4717253cfbd57aadf1af
llvmpipe: avoid generating tri_16 for tris which extend past tile bounds

Don't trim triangle bounding box to scissor/draw-region until after
the logic for emitting tri_16.  Don't generate tri_16 commands for
triangles with untrimmed bounding boxes outside the current tile.

This is important as the tri-16 itself can extend past tile bounds and
we don't want to add code to it to check against tile bounds (slow) or
restrict it to locations within a tile (pessimistic).
src/gallium/drivers/llvmpipe/lp_setup_line.c
src/gallium/drivers/llvmpipe/lp_setup_tri.c