gallium: add PIPE_CAP_TGSI_ATOMFADD to indicate support
ATOMFADD is a little special -- make drivers have to specify it explicitly. Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Reviewed-by: Marek Olšák <marek.olsak@amd.com>
This commit is contained in:
@@ -311,6 +311,7 @@ u_pipe_screen_get_param_defaults(struct pipe_screen *pscreen,
|
||||
case PIPE_CAP_MAX_COMBINED_SHADER_BUFFERS:
|
||||
case PIPE_CAP_MAX_COMBINED_HW_ATOMIC_COUNTERS:
|
||||
case PIPE_CAP_MAX_COMBINED_HW_ATOMIC_COUNTER_BUFFERS:
|
||||
case PIPE_CAP_TGSI_ATOMFADD:
|
||||
return 0;
|
||||
|
||||
case PIPE_CAP_MAX_GS_INVOCATIONS:
|
||||
|
@@ -480,6 +480,8 @@ subpixel precision bias in bits during conservative rasterization.
|
||||
* ``PIPE_CAP_SURFACE_SAMPLE_COUNT_TEXTURE``: Whether the driver
|
||||
supports pipe_surface overrides of resource nr_samples. If set, will
|
||||
enable EXT_multisampled_render_to_texture.
|
||||
* ``PIPE_CAP_TGSI_ATOMFADD``: Atomic floating point adds are supported on
|
||||
images, buffers, and shared memory.
|
||||
|
||||
.. _pipe_capf:
|
||||
|
||||
|
@@ -833,6 +833,7 @@ enum pipe_cap
|
||||
PIPE_CAP_MAX_TEXTURE_UPLOAD_MEMORY_BUDGET,
|
||||
PIPE_CAP_MAX_VERTEX_ELEMENT_SRC_OFFSET,
|
||||
PIPE_CAP_SURFACE_SAMPLE_COUNT,
|
||||
PIPE_CAP_TGSI_ATOMFADD,
|
||||
};
|
||||
|
||||
/**
|
||||
|
Reference in New Issue
Block a user