C Specification
The VkPhysicalDevicePipelineRobustnessPropertiesEXT structure is
defined as:
// Provided by VK_EXT_pipeline_robustness
typedef struct VkPhysicalDevicePipelineRobustnessPropertiesEXT {
VkStructureType sType;
void* pNext;
VkPipelineRobustnessBufferBehaviorEXT defaultRobustnessStorageBuffers;
VkPipelineRobustnessBufferBehaviorEXT defaultRobustnessUniformBuffers;
VkPipelineRobustnessBufferBehaviorEXT defaultRobustnessVertexInputs;
VkPipelineRobustnessImageBehaviorEXT defaultRobustnessImages;
} VkPhysicalDevicePipelineRobustnessPropertiesEXT;
Members
-
sTypeis a VkStructureType value identifying this structure. -
pNextisNULLor a pointer to a structure extending this structure. -
defaultRobustnessStorageBuffersdescribes the behaviour of out of bounds accesses made to storage buffers when no robustness features are enabled -
defaultRobustnessUniformBuffersdescribes the behaviour of out of bounds accesses made to uniform buffers when no robustness features are enabled -
defaultRobustnessVertexInputsdescribes the behaviour of out of bounds accesses made to vertex input attributes when no robustness features are enabled -
defaultRobustnessImagesdescribes the behaviour of out of bounds accesses made to images when no robustness features are enabled
Description
Some implementations of Vulkan may be able to guarantee that certain types of accesses are always performed with robustness even when the Vulkan API’s robustness features are not explicitly enabled.
Even when an implementation reports that accesses to a given resource type are robust by default, it remains invalid to make an out of bounds access without requesting the appropriate robustness feature.
If the VkPhysicalDevicePipelineRobustnessPropertiesEXT structure is included in the pNext chain of the
VkPhysicalDeviceProperties2 structure passed to
vkGetPhysicalDeviceProperties2, it is filled in with each
corresponding implementation-dependent property.
Document Notes
For more information, see the Vulkan Specification
This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.