summaryrefslogtreecommitdiffstats
path: root/src/getopt
diff options
context:
space:
mode:
authorPaul Berry <[email protected]>2012-08-22 08:01:58 -0700
committerPaul Berry <[email protected]>2012-08-24 09:59:27 -0700
commit4b8b6f385e855ecb6da0b7dea56e70e69d1517b9 (patch)
treeda6cc1241645e3cb3ed2e54ed70cb09f7efc45a8 /src/getopt
parent9aacd5cc67ccbc3984bce6a0b40768a6cec2ec2d (diff)
i965/HiZ: remove assertion from intel_resolve_map_set().
There are three possible resolve map states for each (level, layer) of a depth miptree: "needs HiZ resolve", "needs depth resolve", and "needs neither". When HiZ was first implemented on i965, any attempt to directly transition between "needs HiZ resolve" and "needs depth resolve" without passing through the "needs neither" state would have been a bug indicating that a necessary resolve hadn't been performed. Accordingly, intel_resolve_map_set() contained an assertion to verify that no such direct transition happened. However, now that we support fast depth clears, there is a valid transition from the "needs HiZ resolve" to the "needs depth resolve" state. When doing a fast depth clear, the old state of the buffer is irrelevant, since we are completely replacing it with the clear value, so it is not necessary to do any resolves before clearing--we can transition, if necessary, directly from the "needs HiZ resolve" state to the "needs depth resolve" state. To avoid spurious assertions in this valid case, this patch just removes the assertion. Reviewed-by: Eric Anholt <[email protected]> Reviewed-by: Chad Versace <[email protected]>
Diffstat (limited to 'src/getopt')
0 files changed, 0 insertions, 0 deletions