Lines Matching refs:sparse
79 executed "sparse" texture lookup functions.
86 formats required to be supported with sparse textures. These standard
90 * Support for creating sparse multisample and multisample array textures
107 ARB_sparse_texture, to allow for sparse multisample and multisample array
121 size of a sparse texture allocation)
128 is no longer a restriction on the base size of a sparse texture
139 In older extensions supporting sparse textures, the constant
154 initial value (0), the virtual page size for many non-multisample sparse
222 default values, as in non-sparse textures.
244 texture fetch or image load and return sparse texture status information
257 starting with "For levels of a sparse texture where..." to guarantee that
261 For levels of a sparse texture where each dimension is greater than or
286 "sparse" functions are like normal texture lookup functions, except that
287 they return a sparse texture residency status to the caller and return the
291 based on whether sparse functionality is desired. This new variant copies
295 We create a new variant only for the targets for which sparse storage is
658 sparse texture residency information in addition to texel values. In
659 these functions, the sparse texture residency information is returned by
671 Returns false if any of the texels accessed by the sparse texture lookup
715 is a special single-component sparse memory condition code register that
731 SPARSE Update the sparse memory condition code with status on
736 "SPARSE" modifier specifies that the sparse memory condition code
746 RESIDENT sparse resident RESF
747 NONRESIDENT sparse nonresident !RESF
754 sparse condition code. Otherwise, If "0" or "1" is appended ...
764 the sparse memory condition code register if the "SPARSE" instruction
780 - We specify that all loads and atomics from uncommitted sparse memory
783 - We remove the requirement that the base size of a sparse texture
788 - We modify the definition of the sparse texture mipmap tail, so that
803 potential errors when allocating sparse array or cube map textures.
805 - We add support for sparse multisample and multisample array
818 - This extension supports sparse accesses for shadow map sampler types
821 - This extension supports sparse variants of imageLoad(); the AMD
824 - This extension doesn't attempt to support sparse variants of
828 - This extension doesn't attempt to support sparse variants of
853 (3) How should the "sparse" built-in functions return both access status
857 the sparse access status is returned as an integer and the texel values
866 and because we expect that shaders caring to use the "sparse" functions
870 returned by the "sparse" built-in functions?
892 (5) When using a "sparse" built-in texture function, what RGBA values are
897 vector returned by the "sparse" functions for this case should exactly
898 match the vector returned by an equivalent non-"sparse" function.
900 (6) For "sparse" built-in texture functions, where should the <texel>
915 (7) Should we provide sparse variants of the "2DMS" and "2DMSArray"
923 (8) How does the feedback provided in the "sparse" built-in texture
927 RESOLVED: The sparse texture lookup status will indicate that
948 (9) Should we support sparse texel fetches and image loads for buffer
952 extension allowing for the creation and use of sparse buffer resources.
953 Such an extension might also provide the ability to get "sparse"
957 (10) Should we support "sparse" variants of the image atomic functions
969 RESOLVED: We chose not to add any "sparse" variants of
980 that combines four separate "optional" features (sparse, projection,
1013 (12) How does the "reads produce zero" behave if a sparse texture is bound
1034 uncommitted sparse texture whose with a format has no alpha component
1037 non-sparse textures.
1039 (14) Should we provide standard sparse texture page sizes that
1048 standard page size and allow implementations to support sparse textures
1050 page sizes we use arrange sparse textures into 64KB pages and attempt to
1082 TexStorage* to allocate storage for the sparse texture.
1093 (17) Should we support sparse multisample textures? If so, should we
1096 RESOLVED: Yes, we add will support for sparse multisample textures, but
1113 (18) Should we require support for sparse depth or stencil textures?
1120 to support sparse depth/stencil formats, so the only things a change
1142 sparse. For example, the texture() built-in for a sampler type of
1148 We chose to create "sparse" variants of existing built-ins without