BC1: DXT1
BC2: DXT3
BC3: DXT5
-BC5: RGTC
+BC5: RGTC1
BC6H: BPTC float
BC7: BPTC
CS = compute shader: OpenCL-like shader
clear
+ Gallium supports clearing both render targets and depth/stencil with a single call
-draw_range_elements
- + Gallium supports indexed draw with explicit range
-
fence_signalled
fence_finish
+ D3D10/D3D11 don't appear to support explicit fencing; queries can often substitute though, and flushing is supported
set_polygon_stipple
+ Gallium supports polygon stipple
-surface_fill
+clearRT/clearDS
+ Gallium supports subrectangle fills of surfaces, D3D10 only supports full clears of views
* DirectX 10/11 DDI functions and Gallium equivalents
CheckFormatSupport -> screen->is_format_supported
! Gallium passes usages to this function, D3D11 returns them
- Gallium does not differentiate between blendable and non-blendable render targets
- - Gallium lacks multisampled-texture and multisampled-render-target usages
+ ! Gallium includes sample count directly, D3D11 uses additional query
CheckMultisampleQualityLevels
- * could merge this with is_format_supported
- - Gallium lacks multisampling support
+ ! is merged with is_format_supported
CommandListExecute (D3D11 only)
- Gallium does not support command lists
CopyStructureCount (D3D11 only)
- Gallium does not support unordered access views (views that can be written to arbitrarily from compute shaders)
-ClearDepthStencilView -> clear
-ClearRenderTargetView -> clear
+ClearDepthStencilView -> clear_depth_stencil
+ClearRenderTargetView -> clear_render_target
# D3D11 is not totally clear about whether this applies to any view or only a "currently-bound view"
+ Gallium allows to clear both depth/stencil and render target(s) in a single operation
+ Gallium supports double-precision depth values (but not rgba values!)
CreateBlendState (extended in D3D10.1) -> create_blend_state
# D3D10 does not support per-RT blend modes (but per-RT blending), only D3D10.1 does
- - Gallium lacks alpha-to-coverage
+ Gallium supports logic ops
+ Gallium supports dithering
+ Gallium supports using the broadcast alpha component of the blend constant color
+ Gallium has per-face writemask/valuemasks, D3D11 uses the same value for back and front
+ Gallium supports the alpha test, which D3D11 lacks
-CreateDepthStencilView -> get_tex_surface
-CreateRenderTargetView -> get_tex_surface
- ! Gallium merges depthstencil and rendertarget views into pipe_surface, which also doubles as a 2D surface abstraction
- - lack of texture array support
+CreateDepthStencilView -> create_surface
+CreateRenderTargetView -> create_surface
+ ! Gallium merges depthstencil and rendertarget views into pipe_surface
- lack of render-to-buffer support
+ Gallium supports using 3D texture zslices as a depth/stencil buffer (in theory)
! D3D11 has an extra flag (InputSlotClass) that is the same as instance_divisor == 0
CreateGeometryShader -> create_gs_state
-CreateGeometryShaderWithStreamOutput -> create_gs_state
+CreateGeometryShaderWithStreamOutput -> create_gs_state + create_stream_output_state
CreatePixelShader -> create_fs_state
CreateVertexShader -> create_vs_state
> bytecode is different (see D3d10tokenizedprogramformat.hpp)
CheckCounter
CheckCounterInfo
CreateQuery -> create_query
- - Gallium only supports occlusion, primitives generated and primitives emitted queries
! D3D11 implements fences with "event" queries
- * TIMESTAMP could be implemented as an additional fields for other queries: some cards have hardware support for exactly this
- * OCCLUSIONPREDICATE is required for the OpenGL v2 occlusion query functionality
* others are performance counters, we may want them but they are not critical
CreateRasterizerState
- - Gallium lacks clamping of polygon offset depth biases
- - Gallium lacks support to disable depth clipping
- - Gallium lacks multisampling
+ Gallium, like OpenGL, supports PIPE_POLYGON_MODE_POINT
+ Gallium, like OpenGL, supports per-face polygon fill modes
+ Gallium, like OpenGL, supports culling everything
# Note that hardware often has the implicit rule, so the D3D11 interface seems to make little sense
# Also, the D3D11 API does not allow the user to specify mipmap sizes, so this really seems a dubious decision on Microsoft's part
- D3D11 supports specifying initial data to write in the resource
- - Gallium lacks support for stream output buffer usage
- Gallium does not support unordered access buffers
! D3D11 specifies mapping flags (i.e. read/write/discard);:it's unclear what they are used for here
- D3D11 supports odd things in the D3D10_DDI_RESOURCE_MISC_FLAG enum (D3D10_DDI_RESOURCE_MISC_DISCARD_ON_PRESENT, D3D11_DDI_RESOURCE_MISC_BUFFER_ALLOW_RAW_VIEWS, D3D11_DDI_RESOURCE_MISC_BUFFER_STRUCTURED)
- Gallium does not support indirect draw call parameter buffers
- - Gallium lacks multisampling
- - Gallium lacks array textures
! D3D11 supports specifying hardware modes and other stuff here for scanout resources
- + Gallium allows specifying minimum buffer alignment
! D3D11 implements cube maps as 2D array textures
CreateSampler
+ Gallium supports setting min/max/mip filters and anisotropy independently
CreateShaderResourceView (extended in D3D10.1) -> create_sampler_view
- - Gallium lacks sampler views over buffers
- - Gallium lacks texture arrays, and cube map views over texture arrays
+ Gallium supports specifying a swizzle
! D3D11 implements "cube views" as views into a 2D array texture
DispatchIndirect (D3D11 only)
- Gallium does not support compute shaders
-Draw -> draw_arrays
+Draw -> draw_vbo
! D3D11 sets primitive modes separately with IaSetTopology: it's not obvious which is better
-DrawAuto
- - Gallium lacks stream out and DrawAuto
+DrawAuto -> draw_auto
-DrawIndexed -> draw_elements
+DrawIndexed -> draw_vbo
! D3D11 sets primitive modes separately with IaSetTopology: it's not obvious which is better
- * may want to add a separate set_index_buffer
- - Gallium lacks base vertex for indexed draw calls
- + D3D11 lacks draw_range_elements functionality, which is required for OpenGL
+ + D3D11 lacks explicit range, which is required for OpenGL
-DrawIndexedInstanced -> draw_elements_instanced
+DrawIndexedInstanced -> draw_vbo
! D3D11 sets primitive modes separately with IaSetTopology: it's not obvious which is better
- * may want to add a separate set_index_buffer
- - Gallium lacks base vertex for indexed draw calls
-DrawIndexedInstancedIndirect (D3D11 only) -> call draw_elements_instanced multiple times in software
- # this allows to use an hardware buffer to specify the parameters for multiple draw_elements_instanced calls
+DrawIndexedInstancedIndirect (D3D11 only)
+ # this allows to use an hardware buffer to specify the parameters for multiple draw_vbo calls
- Gallium does not support draw call parameter buffers and indirect draw
-DrawInstanced -> draw_arrays_instanced
+DrawInstanced -> draw_vbo
! D3D11 sets primitive modes separately with IaSetTopology: it's not obvious which is better
-DrawInstancedIndirect (D3D11 only) -> call draw_arrays_instanced multiple times in software
- # this allows to use an hardware buffer to specify the parameters for multiple draw_arrays_instanced calls
+DrawInstancedIndirect (D3D11 only)
+ # this allows to use an hardware buffer to specify the parameters for multiple draw_vbo calls
- Gallium does not support draw call parameter buffers and indirect draws
DsSetConstantBuffers (D3D11 only)
- Gallium does not support domain shaders
Flush -> flush
- ! Gallium supports fencing and several kinds of flushing here, D3D11 just has a dumb glFlush-like function
+ ! Gallium supports fencing, D3D11 just has a dumb glFlush-like function
GenMips
- Gallium lacks a mipmap generation interface, and does this manually with the 3D engine
HsSetShaderWithIfaces (D3D11 only)
- Gallium does not support hull shaders
-IaSetIndexBuffer
- ! Gallium passes this to the draw_elements or draw_elements_instanced calls
+IaSetIndexBuffer -> set_index_buffer
+ Gallium supports 8-bit indices
- ! the D3D11 interface allows index-size-unaligned byte offsets into index buffers; it's not clear whether they actually work
+ # the D3D11 interface allows index-size-unaligned byte offsets into the index buffer; most drivers will abort with an assertion
IaSetInputLayout -> bind_vertex_elements_state
+ Gallium supports line loops, triangle fans, quads, quad strips and polygons
IaSetVertexBuffers -> set_vertex_buffers
- + Gallium allows to specify a max_index here
- Gallium only allows setting all vertex buffers at once, while D3D11 supports setting a subset
OpenResource -> texture_from_handle
PsSetShaderWithIfaces (D3D11 only)
- Gallium does not support shader interfaces
-PsSetShaderResources -> set_fragment_sampler_views
+PsSetShaderResources -> set_sampler_views
* may want to allow binding subsets instead of all at once
QueryBegin -> begin_query
ResourceCopyRegion
ResourceConvert (D3D10.1+ only)
ResourceConvertRegion (D3D10.1+ only)
- -> surface_copy
- - Gallium does not support hardware buffer copies
- - Gallium does not support copying 3D texture subregions in a single call
+ -> resource_copy_region
-ResourceIsStagingBusy -> is_texture_referenced, is_buffer_referenced
- - Gallium does not support checking reference for a whole texture, but only a specific surface
+ResourceIsStagingBusy ->
+ - Gallium lacks this
+ + Gallium can use fences
ResourceReadAfterWriteHazard
- ! Gallium specifies hides this, except for the render and texture caches
+ - Gallium lacks this
-ResourceResolveSubresource
- - Gallium does not support multisample sample resolution
+ResourceResolveSubresource -> blit
ResourceMap
ResourceUnmap
DynamicResourceUnmap
StagingResourceMap
StagingResourceUnmap
- -> buffer_map / buffer_unmap
-> transfer functions
! Gallium and D3D have different semantics for transfers
* D3D separates vertex/index buffers from constant buffers
ResourceUpdateSubresourceUP -> transfer functionality, transfer_inline_write in gallium-resources
DefaultConstantBufferUpdateSubresourceUP -> transfer functionality, transfer_inline_write in gallium-resources
-SetBlendState -> bind_blend_state and set_blend_color
- ! D3D11 fuses bind_blend_state and set_blend_color in a single function
- - Gallium lacks the sample mask
+SetBlendState -> bind_blend_state, set_blend_color and set_sample_mask
+ ! D3D11 fuses bind_blend_state, set_blend_color and set_sample_mask in a single function
SetDepthStencilState -> bind_depth_stencil_alpha_state and set_stencil_ref
! D3D11 fuses bind_depth_stencil_alpha_state and set_stencil_ref in a single function
- Gallium does not support unordered access views
- Gallium does not support geometry shader selection of texture array image / 3D texture zslice
-SetResourceMinLOD (D3D11 only)
- - Gallium does not support min lod directly on textures
+SetResourceMinLOD (D3D11 only) -> pipe_sampler_view::tex::first_level
SetScissorRects
- Gallium lacks support for multiple geometry-shader-selectable scissor rectangles D3D11 has
SetViewports
- Gallium lacks support for multiple geometry-shader-selectable viewports D3D11 has
-ShaderResourceViewReadAfterWriteHazard -> flush(PIPE_FLUSH_RENDER_CACHE)
- - Gallium does not support specifying this per-render-target/view
+ShaderResourceViewReadAfterWriteHazard
+ - Gallium lacks support for this
+ + Gallium has texture_barrier
-SoSetTargets
- - Gallium does not support stream out
+SoSetTargets -> set_stream_output_buffers
VsSetConstantBuffers -> for(i = StartBuffer; i < NumBuffers; ++i) set_constant_buffer(PIPE_SHADER_VERTEX, i, phBuffers[i])
* may want to split into fragment/vertex-specific versions
VsSetShaderWithIfaces (D3D11 only)
- Gallium does not support shader interfaces
-VsSetShaderResources -> set_fragment_sampler_views
+VsSetShaderResources -> set_sampler_views
* may want to allow binding subsets instead of all at once
projects / mesa.git / blobdiff