vkDestroyIndirectCommandsLayoutEXT

Indirect command layouts for VK_EXT_device_generated_commands are destroyed by:

void vkDestroyIndirectCommandsLayoutEXT(
    VkDevice device,
    VkIndirectCommandsLayoutEXT indirectCommandsLayout,
    const VkAllocationCallbacks* pAllocator);

device is the logical device that destroys the layout.
indirectCommandsLayout is the layout to destroy.
pAllocator controls host memory allocation as described in the Memory Allocation chapter.

Valid Usage

VUID-vkDestroyIndirectCommandsLayoutEXT-indirectCommandsLayout-11114

All submitted commands that refer to indirectCommandsLayout must have completed execution

VUID-vkDestroyIndirectCommandsLayoutEXT-indirectCommandsLayout-11115

If VkAllocationCallbacks were provided when indirectCommandsLayout was created, a compatible set of callbacks must be provided here

VUID-vkDestroyIndirectCommandsLayoutEXT-indirectCommandsLayout-11116

If no VkAllocationCallbacks were provided when indirectCommandsLayout was created, pAllocator must be NULL

Valid Usage (Implicit)

VUID-vkDestroyIndirectCommandsLayoutEXT-device-parameter

device must be a valid VkDevice handle

VUID-vkDestroyIndirectCommandsLayoutEXT-indirectCommandsLayout-parameter

If indirectCommandsLayout is not VK_NULL_HANDLE, indirectCommandsLayout must be a valid VkIndirectCommandsLayoutEXT handle

VUID-vkDestroyIndirectCommandsLayoutEXT-pAllocator-parameter

If pAllocator is not NULL, pAllocator must be a valid pointer to a valid VkAllocationCallbacks structure

VUID-vkDestroyIndirectCommandsLayoutEXT-indirectCommandsLayout-parent

If indirectCommandsLayout is a valid handle, it must have been created, allocated, or retrieved from device

Host Synchronization

Host access to indirectCommandsLayout must be externally synchronized ::