| Safe Haskell | None |
|---|---|
| Language | Haskell2010 |
Vulkan.Extensions.VK_EXT_robustness2
Description
Name
VK_EXT_robustness2 - device extension
VK_EXT_robustness2
- Name String
VK_EXT_robustness2
- Extension Type
- Device extension
- Registered Extension Number
- 287
- Revision
- 1
- Extension and Version Dependencies
- Requires Vulkan 1.0
- Contact
Other Extension Metadata
- Last Modified Date
- 2020-01-29
- IP Status
- No known IP claims.
- Contributors
- Liam Middlebrook, NVIDIA
- Jeff Bolz, NVIDIA
Description
This extension adds stricter requirements for how out of bounds reads and writes are handled. Most accesses must be tightly bounds-checked, out of bounds writes must be discarded, out of bound reads must return zero. Rather than allowing multiple possible (0,0,0,x) vectors, the out of bounds values are treated as zero, and then missing components are inserted based on the format as described in Conversion to RGBA and vertex input attribute extraction.
These additional requirements may be expensive on some implementations, and should only be enabled when truly necessary.
This extension also adds support for "null descriptors", where
NULL_HANDLE can be used instead of a
valid handle. Accesses to null descriptors have well-defined behavior,
and don’t rely on robustness.
New Structures
New Enum Constants
EXT_ROBUSTNESS_2_SPEC_VERSIONExtending
StructureType:
Issues
- Why do
PhysicalDeviceRobustness2PropertiesEXT::robustUniformBufferAccessSizeAlignmentandPhysicalDeviceRobustness2PropertiesEXT::robustStorageBufferAccessSizeAlignmentexist?
RESOLVED: Some implementations can’t efficiently tightly bounds-check all buffer accesses. Rather, the size of the bound range is padded to some power of two multiple, up to 256 bytes for uniform buffers and up to 4 bytes for storage buffers, and that padded size is bounds-checked. This is sufficient to implement D3D-like behavior, because D3D only allows binding whole uniform buffers or ranges that are a multiple of 256 bytes, and D3D raw and structured buffers only support 32-bit accesses.
Examples
None.
Version History
Revision 1, 2019-11-01 (Jeff Bolz, Liam Middlebrook)
- Initial draft
See Also
PhysicalDeviceRobustness2FeaturesEXT,
PhysicalDeviceRobustness2PropertiesEXT
Document Notes
For more information, see the Vulkan Specification
This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.
Synopsis
- data PhysicalDeviceRobustness2FeaturesEXT = PhysicalDeviceRobustness2FeaturesEXT {}
- data PhysicalDeviceRobustness2PropertiesEXT = PhysicalDeviceRobustness2PropertiesEXT {}
- type EXT_ROBUSTNESS_2_SPEC_VERSION = 1
- pattern EXT_ROBUSTNESS_2_SPEC_VERSION :: forall a. Integral a => a
- type EXT_ROBUSTNESS_2_EXTENSION_NAME = "VK_EXT_robustness2"
- pattern EXT_ROBUSTNESS_2_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a
Documentation
data PhysicalDeviceRobustness2FeaturesEXT Source #
VkPhysicalDeviceRobustness2FeaturesEXT - Structure describing the out-of-bounds behavior for an implementation
Members
The members of the PhysicalDeviceRobustness2FeaturesEXT structure
describe the following features:
Description
-
robustBufferAccess2indicates whether buffer accesses are tightly bounds-checked against the range of the descriptor. Uniform buffers must be bounds-checked to the range of the descriptor, where the range is rounded up to a multiple of robustUniformBufferAccessSizeAlignment. Storage buffers must be bounds-checked to the range of the descriptor, where the range is rounded up to a multiple of robustStorageBufferAccessSizeAlignment. Out of bounds buffer loads will return zero values, and formatted loads will have (0,0,1) values inserted for missing G, B, or A components based on the format.
-
robustImageAccess2indicates whether image accesses are tightly bounds-checked against the dimensions of the image view. Out of bounds image loads will return zero values, with (0,0,1) values inserted for missing G, B, or A components based on the format. -
nullDescriptorindicates whether descriptors can be written with aNULL_HANDLEresource or view, which are considered valid to access and act as if the descriptor were bound to nothing.
If the PhysicalDeviceRobustness2FeaturesEXT structure is included in
the pNext chain of
PhysicalDeviceFeatures2,
it is filled with values indicating whether each feature is supported.
Valid Usage
-
If
robustBufferAccess2is enabled then robustBufferAccess must also be enabled
Valid Usage (Implicit)
-
sTypemust beSTRUCTURE_TYPE_PHYSICAL_DEVICE_ROBUSTNESS_2_FEATURES_EXT
See Also
Constructors
| PhysicalDeviceRobustness2FeaturesEXT | |
Fields | |
Instances
data PhysicalDeviceRobustness2PropertiesEXT Source #
VkPhysicalDeviceRobustness2PropertiesEXT - Structure describing robust buffer access properties supported by an implementation
Members
The members of the PhysicalDeviceRobustness2PropertiesEXT structure
describe the following implementation-dependent limits:
Description
If the PhysicalDeviceRobustness2PropertiesEXT structure is included in
the pNext chain of
PhysicalDeviceProperties2,
it is filled with the implementation-dependent limits.
Valid Usage (Implicit)
See Also
Constructors
| PhysicalDeviceRobustness2PropertiesEXT | |
Fields
| |
Instances
type EXT_ROBUSTNESS_2_SPEC_VERSION = 1 Source #
pattern EXT_ROBUSTNESS_2_SPEC_VERSION :: forall a. Integral a => a Source #
type EXT_ROBUSTNESS_2_EXTENSION_NAME = "VK_EXT_robustness2" Source #
pattern EXT_ROBUSTNESS_2_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a Source #