diff options
author | Kenneth Graunke <[email protected]> | 2015-12-17 21:02:40 -0800 |
---|---|---|
committer | Kenneth Graunke <[email protected]> | 2015-12-22 17:22:00 -0800 |
commit | f46dbfaed914e0e3463f3a28fc877695cd7e7834 (patch) | |
tree | a59147c886d7551acbc630cab03cd7e3c25b8424 /src/mesa/drivers/dri/i965/brw_vs.c | |
parent | 8498cb4a45e8ed53a2ee2b35d3c2cbb9963e1756 (diff) |
i965: Consolidate BRW_NEW_TESS_{CTRL,EVAL}_PROGRAM flags.
For several reasons, I don't think it's particularly useful to have
separate flags:
1. Most of the time, tessellation shaders are paired, so both will be
replaced at the same time.
2. The data layout is tightly coupled. Both need to agree on the number
of per-patch slots in the VUE map. Even adding extra TCS outputs
that aren't read by the TES will trigger the need for recompiles.
3. The TCS is optional from an API perspective, but required by the
hardware whenever tessellation is enabled. So, atoms that deal with
the TCS must check brw->tess_eval_program (BRW_NEW_TESS_EVAL_PROGRAM?)
rather than brw->tess_ctrl_program to tell whether tessellation is
enabled.
So, not only is it unlikely to be useful, it's a bit confusing to get
right. Simply using one flag for both simplifies this.
Signed-off-by: Kenneth Graunke <[email protected]>
Reviewed-by: Jordan Justen <[email protected]>
Diffstat (limited to 'src/mesa/drivers/dri/i965/brw_vs.c')
0 files changed, 0 insertions, 0 deletions