From 3f6b3d9db72c45e648c8c5943ef949273b110005 Mon Sep 17 00:00:00 2001 From: Nicolai Hähnle Date: Tue, 12 Sep 2017 18:46:46 +0200 Subject: gallium: add PIPE_QUERY_OCCLUSION_PREDICATE_CONSERVATIVE MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit To be able to properly distinguish between GL_ANY_SAMPLES_PASSED and GL_ANY_SAMPLES_PASSED_CONSERVATIVE. This patch goes through all drivers, having them treat the two query types identically, except: 1. radeon incorrectly enabled conservative mode on PIPE_QUERY_OCCLUSION_PREDICATE. We now do it correctly, only on PIPE_QUERY_OCCLUSION_PREDICATE_CONSERVATIVE. 2. st/mesa uses the new query type. Fixes dEQP-GLES31.functional.fbo.no_attachments.* Reviewed-by: Marek Olšák --- src/gallium/docs/source/context.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/gallium/docs') diff --git a/src/gallium/docs/source/context.rst b/src/gallium/docs/source/context.rst index 6ac45819a66..ba7fef8301d 100644 --- a/src/gallium/docs/source/context.rst +++ b/src/gallium/docs/source/context.rst @@ -394,6 +394,12 @@ value of FALSE for cases where COUNTER would result in 0 and TRUE for all other cases. This query can be used with ``render_condition``. +In cases where a conservative approximation of an occlusion query is enough, +``PIPE_QUERY_OCCLUSION_PREDICATE_CONSERVATIVE`` should be used. It behaves +like ``PIPE_QUERY_OCCLUSION_PREDICATE``, except that it may return TRUE in +additional, implementation-dependent cases. +This query can be used with ``render_condition``. + ``PIPE_QUERY_TIME_ELAPSED`` returns the amount of time, in nanoseconds, the context takes to perform operations. The result is an unsigned 64-bit integer. -- cgit v1.2.3