Structures
VkPhysicalDeviceMaintenance8FeaturesKHR
Structure describing whether the implementation supports maintenance8 functionality
The VkPhysicalDeviceMaintenance8FeaturesKHR structure is defined as:
typedef struct VkPhysicalDeviceMaintenance8FeaturesKHR {
VkStructureType sType;
void* pNext;
VkBool32 maintenance8;
} VkPhysicalDeviceMaintenance8FeaturesKHR;
This structure describes the following feature:
sTypeis a VkStructureType value identifying this structure.pNextisNULLor a pointer to a structure extending this structure.-
maintenance8indicates that the implementation supports the following: - Allow copies between depth/stencil and
matchingcolor attachments - Allow
dstCacheinvkMergePipelineCachesto be implicitly synchronized. - Require src/dst sync scopes to work when doing queue family ownership transfers
- Support
Offset(as an alternative toConstOffset) image operand in texture sampling and fetch operations - Use the SPIR-V definition of OpSRem and OpSMod, making these operations produce well-defined results for negative operands
- Loosen layer restrictions when blitting from 3D images to other image types
- Add space for an additional 64 access flags for use with VkMemoryBarrier2, VkBufferMemoryBarrier2, and VkImageMemoryBarrier2
-
If the VkPhysicalDeviceMaintenance8FeaturesKHR structure is included in the pNext chain of the
VkPhysicalDeviceFeatures2 structure passed to
vkGetPhysicalDeviceFeatures2, it is filled in to indicate whether each
corresponding feature is supported.
If the application wishes to use a VkDevice with any features
described by VkPhysicalDeviceMaintenance8FeaturesKHR, it must add an instance of the structure,
with the desired feature members set to VK_TRUE, to the pNext
chain of VkDeviceCreateInfo when creating the VkDevice.
Valid Usage (Implicit)
VUID-VkPhysicalDeviceMaintenance8FeaturesKHR-sType-sType
sType must be VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MAINTENANCE_8_FEATURES_KHR