Function Prototype

vkDestroyIndirectCommandsLayoutNV

Destroy an indirect commands layout

Indirect command layouts are destroyed by:

void vkDestroyIndirectCommandsLayoutNV(
    VkDevice device,
    VkIndirectCommandsLayoutNV 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-vkDestroyIndirectCommandsLayoutNV-indirectCommandsLayout-02938

All submitted commands that refer to indirectCommandsLayout must have completed execution

VUID-vkDestroyIndirectCommandsLayoutNV-indirectCommandsLayout-02939

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

VUID-vkDestroyIndirectCommandsLayoutNV-indirectCommandsLayout-02940

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

VUID-vkDestroyIndirectCommandsLayoutNV-deviceGeneratedCommands-02941

The VkPhysicalDeviceDeviceGeneratedCommandsFeaturesNV::deviceGeneratedCommands feature must be enabled

Valid Usage (Implicit)

VUID-vkDestroyIndirectCommandsLayoutNV-device-parameter

device must be a valid VkDevice handle

VUID-vkDestroyIndirectCommandsLayoutNV-indirectCommandsLayout-parameter

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

VUID-vkDestroyIndirectCommandsLayoutNV-pAllocator-parameter

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

VUID-vkDestroyIndirectCommandsLayoutNV-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 ::