vkDestroyIndirectExecutionSetEXT(3)

# vkDestroyIndirectExecutionSetEXT(3) Manual Page

## Name

vkDestroyIndirectExecutionSetEXT - Destroy an indirect execution set

Loading… please wait.

## C Specification

Destroy an Indirect Execution Set by calling:

    // Provided by VK_EXT_device_generated_commands
    void vkDestroyIndirectExecutionSetEXT(
        VkDevice                                    device,
        VkIndirectExecutionSetEXT                   indirectExecutionSet,
        const VkAllocationCallbacks*                pAllocator);

## Parameters

- `device` is the logical device that owns the indirect execution set.

- `indirectExecutionSet` is the indirect execution set to destroy.

- `pAllocator` controls host memory allocation as described in the Memory Allocation chapter.

## Description

Valid Usage

- VUID-vkDestroyIndirectExecutionSetEXT-indirectExecutionSet-11025
  All submitted commands that refer to `indirectExecutionSet` must have completed execution

Valid Usage (Implicit)

- VUID-vkDestroyIndirectExecutionSetEXT-device-parameter
  `device` must be a valid VkDevice handle

- VUID-vkDestroyIndirectExecutionSetEXT-indirectExecutionSet-parameter
  If `indirectExecutionSet` is not VK_NULL_HANDLE, `indirectExecutionSet` must be a valid VkIndirectExecutionSetEXT handle

- VUID-vkDestroyIndirectExecutionSetEXT-pAllocator-parameter
  If `pAllocator` is not `NULL`, `pAllocator` must be a valid pointer to a valid VkAllocationCallbacks structure

- VUID-vkDestroyIndirectExecutionSetEXT-indirectExecutionSet-parent
  If `indirectExecutionSet` is a valid handle, it must have been created, allocated, or retrieved from `device`

Host Synchronization

- Host access to `indirectExecutionSet` must be externally synchronized

## See Also

VK_EXT_device_generated_commands, VkAllocationCallbacks, VkDevice, VkIndirectExecutionSetEXT

## 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.

## Copyright

Copyright 2014-2025 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0