mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
* 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).
88 lines
2.9 KiB
Plaintext
88 lines
2.9 KiB
Plaintext
// Copyright (c) 2016-2019 Khronos Group. This work is licensed under a
|
|
// Creative Commons Attribution 4.0 International License; see
|
|
// http://creativecommons.org/licenses/by/4.0/
|
|
|
|
include::meta/VK_KHR_variable_pointers.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2017-09-05
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Interactions and External Dependencies*::
|
|
- Requires the
|
|
{spirv}/KHR/SPV_KHR_variable_pointers.html[`SPV_KHR_variable_pointers`]
|
|
SPIR-V extension.
|
|
- Promoted to Vulkan 1.1 Core
|
|
*Contributors*::
|
|
- John Kessenich, Google
|
|
- Neil Henning, Codeplay
|
|
- David Neto, Google
|
|
- Daniel Koch, Nvidia
|
|
- Graeme Leese, Broadcom
|
|
- Weifeng Zhang, Qualcomm
|
|
- Stephen Clarke, Imagination Technologies
|
|
- Jason Ekstrand, Intel
|
|
- Jesse Hall, Google
|
|
|
|
The `VK_KHR_variable_pointers` extension allows implementations to indicate
|
|
their level of support for the `SPV_KHR_variable_pointers` SPIR-V extension.
|
|
The SPIR-V extension allows shader modules to use invocation-private
|
|
pointers into uniform and/or storage buffers, where the pointer values can
|
|
be dynamic and non-uniform.
|
|
|
|
The `SPV_KHR_variable_pointers` extension introduces two capabilities.
|
|
The first, code:VariablePointersStorageBuffer, must: be supported by all
|
|
implementations of this extension.
|
|
The second, code:VariablePointers, is optional.
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VARIABLE_POINTER_FEATURES_KHR
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkPhysicalDeviceVariablePointersFeaturesKHR
|
|
|
|
=== New SPIR-V Capabilities
|
|
|
|
* <<spirvenv-capabilities-table-variablepointers,VariablePointersStorageBuffer>>
|
|
* <<spirvenv-capabilities-table-variablepointers,VariablePointers>>
|
|
|
|
=== Promotion to Vulkan 1.1
|
|
|
|
All functionality in this extension is included in core Vulkan 1.1, with the
|
|
KHR suffix omitted, however support for the
|
|
<<features-variablePointersStorageBuffer,
|
|
pname:variablePointersStorageBuffer>> feature is made optional.
|
|
The original type, enum and command names are still available as aliases of
|
|
the core functionality.
|
|
|
|
=== Issues
|
|
|
|
1) Do we need an optional property for the SPIR-V
|
|
code:VariablePointersStorageBuffer capability or should it be mandatory when
|
|
this extension is advertised?
|
|
|
|
*RESOLVED*: Add it as a distinct feature, but make support mandatory.
|
|
Adding it as a feature makes the extension easier to include in a future
|
|
core API version.
|
|
In the extension, the feature is mandatory, so that presence of the
|
|
extension guarantees some functionality.
|
|
When included in a core API version, the feature would be optional.
|
|
|
|
2) Can support for these capabilities vary between shader stages?
|
|
|
|
*RESOLVED*: No, if the capability is supported in any stage it must be
|
|
supported in all stages.
|
|
|
|
3) Should the capabilities be features or limits?
|
|
|
|
*RESOLVED*: Features, primarily for consistency with other similar
|
|
extensions.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2017-03-14 (Jesse Hall and John Kessenich)
|
|
- Internal revisions
|