mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
521e98405f
* Update release number to 120.
Github Issues:
* Add slink:VkAccelerationStructureTypeNV explicitly to extension XML for
`<<VK_NV_ray_tracing>>` (public issue 848).
* Add missing valid usage statements for feature flags in
slink:VkCommandBufferInheritanceInfo (public pull request 1017).
Internal Issues:
* Clarify behavior of non-premultiplied destination colors for
`<<VK_EXT_blend_operation_advanced>>` prior to the definition of
slink:VkBlendOverlapEXT (internal issue 1766).
* Fix the confusing phrasing "`no other queue must: be (doing something)`"
for flink:vkQueuePresentKHR, flink:vkQueueSubmit, and
flink:vkQueueBindSparse (internal issue 1774).
* Add `<<VK_EXT_validation_features>>` flag to enable best practices
checks, which will soon be available in the validation layer (internal
issue 1779).
* Specify allowed characters for VUID tag name components in the style
guide (internal issue 1788).
* Update links to SPIR-V extension specifications, and parameterize their
markup in case the URLs change in the future (internal issue 1797).
* Fix an off-by-one error in the valid usage statement for
slink:VkPipelineExecutableInfoKHR (internal merge request 3303).
* Clean up markup indentation not matching the style guide (internal merge
request 3314).
* Minor script updates to allow refpage aliases, generate a dynamic TOC
for refpages, generate Apache rewrite rules for aliases, open external
links from refpages in a new window, and synchronize with the OpenCL
scripts. This will shortly enable a paned navigation setup for refpages,
similar to the OpenCL 2.2 refpages (internal merge request 3322).
* Script updates to add tests to the checker, refactor and reformat code,
generate better text for some valid usage statements, use more Pythonic
idioms, and synchronize with the OpenXR scripts (internal merge request
3239).
* Script updates and minor fixes in spec language to not raise checker
errors for refpage markup of pages not existing in the API, such as
VKAPI_NO_STDINT_H. Remove corresponding suppression of some
check_spec_links.py tests from .gitlab-ci.yml and 'allchecks' target
(internal merge request 3315).
69 lines
1.7 KiB
Plaintext
69 lines
1.7 KiB
Plaintext
include::meta/VK_NV_compute_shader_derivatives.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2018-07-19
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- Pat Brown, NVIDIA
|
|
|
|
This extension adds Vulkan support for the
|
|
{spirv}/NV/SPV_NV_compute_shader_derivatives.html[`SPV_NV_compute_shader_derivatives`]
|
|
SPIR-V extension.
|
|
|
|
The SPIR-V extension provides two new execution modes, both of which allow
|
|
compute shaders to use built-ins that evaluate compute derivatives
|
|
explicitly or implicitly.
|
|
Derivatives will be computed via differencing over a 2x2 group of shader
|
|
invocations.
|
|
The code:DerivativeGroupQuadsNV execution mode assembles shader invocations
|
|
into 2x2 groups, where each group has x and y coordinates of the local
|
|
invocation ID of the form (2m+{0,1}, 2n+{0,1}).
|
|
The code:DerivativeGroupLinearNV execution mode assembles shader invocations
|
|
into 2x2 groups, where each group has local invocation index values of the
|
|
form 4m+{0,1,2,3}.
|
|
|
|
=== New Object Types
|
|
|
|
None.
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_COMPUTE_SHADER_DERIVATIVES_FEATURES_NV
|
|
|
|
=== New Enums
|
|
|
|
None.
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkPhysicalDeviceComputeShaderDerivativesFeaturesNV
|
|
|
|
=== New Functions
|
|
|
|
None.
|
|
|
|
=== New SPIR-V Capability
|
|
|
|
* <<spirvenv-capabilities-table-computederivatives-quads,ComputeDerivativeGroupQuadsNV>>
|
|
* <<spirvenv-capabilities-table-computederivatives-linear,ComputeDerivativeGroupLinearNV>>
|
|
|
|
=== Issues
|
|
|
|
(1) Should we specify that the groups of four shader invocations used for
|
|
derivatives in a compute shader are the same groups of four invocations
|
|
that form a "`quad`" in shader subgroups?
|
|
|
|
*RESOLVED*: Yes.
|
|
|
|
|
|
=== Examples
|
|
|
|
None.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2018-07-19 (Pat Brown)
|
|
- Initial draft
|