C Specification
The VkPhysicalDeviceMaintenance8FeaturesKHR
structure is defined as:
// Provided by VK_KHR_maintenance8
typedef struct VkPhysicalDeviceMaintenance8FeaturesKHR {
VkStructureType sType;
void* pNext;
VkBool32 maintenance8;
} VkPhysicalDeviceMaintenance8FeaturesKHR;
Members
This structure describes the following feature:
-
sType
is a VkStructureType value identifying this structure. -
pNext
isNULL
or a pointer to a structure extending this structure.-
maintenance8
indicates that the implementation supports the following: -
Allow copies between depth/stencil and “matching” color attachments
-
Allow
dstCache
invkMergePipelineCaches
to 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
-
Description
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.
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.