vkCreatePipelineBinariesKHR - Create pipeline binaries from a pipeline or previously retrieved data

Description

The implementation will attempt to create all pipeline binaries. If creation fails for any pipeline binary, then:

• The corresponding entry in the pPipelineBinaries output array will be filled with NULL_HANDLE.
• The Result returned by createPipelineBinariesKHR will contain the error value for the first entry in the output array in pBinaries containing NULL_HANDLE.

Valid Usage (Implicit)

• device must be a valid Device handle

• pCreateInfo must be a valid pointer to a valid PipelineBinaryCreateInfoKHR structure
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid AllocationCallbacks structure
• pBinaries must be a valid pointer to a PipelineBinaryHandlesInfoKHR structure

Return Codes

Success

• SUCCESS
• INCOMPLETE
• PIPELINE_BINARY_MISSING_KHR

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY
• ERROR_INITIALIZATION_FAILED

See Also

VK_KHR_pipeline_binary, AllocationCallbacks, Device, PipelineBinaryCreateInfoKHR, PipelineBinaryHandlesInfoKHR

vkDestroyPipelineBinaryKHR - Destroy a pipeline binary

Valid Usage

• If AllocationCallbacks were provided when pipelineBinary was created, a compatible set of callbacks must be provided here

• If no AllocationCallbacks were provided when pipelineBinary was created, pAllocator must be NULL

Valid Usage (Implicit)

• device must be a valid Device handle

• If pipelineBinary is not NULL_HANDLE, pipelineBinary must be a valid PipelineBinaryKHR handle
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid AllocationCallbacks structure
• If pipelineBinary is a valid handle, it must have been created, allocated, or retrieved from device

Host Synchronization

• Host access to pipelineBinary must be externally synchronized

See Also

VK_KHR_pipeline_binary, AllocationCallbacks, Device, PipelineBinaryKHR

vkGetPipelineKeyKHR - Generate the pipeline key from pipeline creation info

Description

If pPipelineCreateInfo is NULL, then the implementation must return the global key that applies to all pipelines. If the key obtained in this way changes between saving and restoring data obtained from getPipelineBinaryDataKHR in a different Device, then the application must assume that the restored data is invalid and cannot be passed to createPipelineBinariesKHR. Otherwise the application can assume the data is still valid.

If pPipelineCreateInfo is not NULL, the key obtained functions as a method to compare two pipeline creation info structures. Implementations may not compare parts of a pipeline creation info which would not contribute to the final binary output. If a shader module identifier is used instead of a shader module, the pPipelineKey generated must be equal to the key generated when using the shader module from which the identifier was queried. If the content of two pPipelineKey are equal, pipelines created with the two pPipelineCreateInfo->pname:pNext create infos must produce the same PipelineBinaryKHR contents.

The pipeline key is distinct from pipeline binary key. Pipeline binary keys can only be obtained after compilation. The pipeline key is intended to optionally allow associating pipeline create info with multiple pipeline binary keys.

Valid Usage

• The pNext chain of pPipelineCreateInfo must not set PipelineBinaryInfoKHR::binaryCount to a value greater than 0

Valid Usage (Implicit)

• device must be a valid Device handle

• If pPipelineCreateInfo is not NULL, pPipelineCreateInfo must be a valid pointer to a valid PipelineCreateInfoKHR structure
• pPipelineKey must be a valid pointer to a PipelineBinaryKeyKHR structure

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

VK_KHR_pipeline_binary, Device, PipelineBinaryKeyKHR, PipelineCreateInfoKHR

vkGetPipelineBinaryDataKHR - Get the data store from a pipeline binary

Description

If pPipelineBinaryData is NULL, then the size of the data, in bytes, that is required to store the binary is returned in pPipelineBinaryDataSize. Otherwise, pPipelineBinaryDataSize must contain the size of the buffer, in bytes, pointed to by pPipelineBinaryData, and on return pPipelineBinaryDataSize is overwritten with the size of the data, in bytes, that is required to store the binary. If pPipelineBinaryDataSize is less than the size that is required to store the binary, nothing is written to pPipelineBinaryData and ERROR_NOT_ENOUGH_SPACE_KHR will be returned, instead of SUCCESS.

If pipelineBinaryCompressedData is FALSE, implementations should not return compressed pipeline binary data to the application.

Valid Usage (Implicit)

• device must be a valid Device handle

• pInfo must be a valid pointer to a valid PipelineBinaryDataInfoKHR structure
• pPipelineBinaryKey must be a valid pointer to a PipelineBinaryKeyKHR structure
• pPipelineBinaryDataSize must be a valid pointer to a size_t value
• If the value referenced by pPipelineBinaryDataSize is not 0, and pPipelineBinaryData is not NULL, pPipelineBinaryData must be a valid pointer to an array of pPipelineBinaryDataSize bytes

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY
• ERROR_NOT_ENOUGH_SPACE_KHR

See Also

VK_KHR_pipeline_binary, Device, PipelineBinaryDataInfoKHR, PipelineBinaryKeyKHR

vkReleaseCapturedPipelineDataKHR - Release captured pipeline binary data

Description

The implementation may free any resources captured as a result of creating the pipeline with PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR and put the pipeline into a state as if PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR had not been provided at pipeline creation time.

Any resources captured as a result of creating the pipeline with PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR are implicitly freed by destroyPipeline.

Valid Usage

• If AllocationCallbacks were provided when pipeline was created, a compatible set of callbacks must be provided in pAllocator

• If no AllocationCallbacks were provided when pipeline was created, pAllocator must be NULL

Valid Usage (Implicit)

• device must be a valid Device handle

• pInfo must be a valid pointer to a valid ReleaseCapturedPipelineDataInfoKHR structure
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid AllocationCallbacks structure

Host Synchronization

• Host access to pInfo->pipeline must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

None

See Also

VK_KHR_pipeline_binary, AllocationCallbacks, Device, ReleaseCapturedPipelineDataInfoKHR

VkPipelineBinaryCreateInfoKHR - Structure specifying where to retrieve data for pipeline binary creation

Description

When pPipelineCreateInfo is not NULL, an implementation will attempt to retrieve pipeline binary data from an internal cache external to the application if pipelineBinaryInternalCache is TRUE. Applications can use this to determine if a pipeline can be created without compilation. If the implementation fails to create a pipeline binary due to missing an internal cache entry, PIPELINE_BINARY_MISSING_KHR is returned. If creation succeeds, the resulting binary can be used to create a pipeline. PIPELINE_BINARY_MISSING_KHR may be returned for any reason in this situation, even if creating a pipeline binary with the same parameters that succeeded earlier.

If pipelineBinaryPrecompiledInternalCache is TRUE, the implementation may be able to create pipeline binaries even when pPipelineCreateInfo has not been used to create binaries before by the application.

On some platforms, internal pipeline caches may be pre-populated before running the application.

Valid Usage

• If pipeline is not NULL_HANDLE, pipeline must have been created with PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR

• If pipeline is not NULL_HANDLE, releaseCapturedPipelineDataKHR must not have been called on pipeline prior to this command
• If pipelineBinaryInternalCache is FALSE pPipelineCreateInfo must be NULL
• If device was created with DevicePipelineBinaryInternalCacheControlKHR::disableInternalCache set to TRUE, pPipelineCreateInfo must be NULL
• One and only one of pKeysAndDataInfo, pipeline, or pPipelineCreateInfo must be non-NULL
• If pPipelineCreateInfo is not NULL, the pNext chain of pPipelineCreateInfo must not set PipelineBinaryInfoKHR::binaryCount to a value greater than 0

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_PIPELINE_BINARY_CREATE_INFO_KHR

• pNext must be NULL
• If pKeysAndDataInfo is not NULL, pKeysAndDataInfo must be a valid pointer to a valid PipelineBinaryKeysAndDataKHR structure
• If pipeline is not NULL_HANDLE, pipeline must be a valid Pipeline handle
• If pPipelineCreateInfo is not NULL, pPipelineCreateInfo must be a valid pointer to a valid PipelineCreateInfoKHR structure

See Also

VK_KHR_pipeline_binary, Pipeline, PipelineBinaryKeysAndDataKHR, PipelineCreateInfoKHR, StructureType, createPipelineBinariesKHR

VkPipelineBinaryHandlesInfoKHR - Structure containing newly created pipeline binaries

Description

If pPipelineBinaries is NULL, the number of binaries that would be created is returned in pipelineBinaryCount. Otherwise, pipelineBinaryCount must be the number of entries in the pPipelineBinaries array, and on return from createPipelineBinariesKHR pipelineBinaryCount is overwritten with the number of handles actually written to pPipelineBinaries. If the value of pipelineBinaryCount is less than the number of binaries that would have been created, at most pipelineBinaryCount handles will be written to pPipelineBinaries and INCOMPLETE will be returned instead of SUCCESS, to indicate that pPipelineBinaries was not large enough to create all the binaries.

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_PIPELINE_BINARY_HANDLES_INFO_KHR

• pNext must be NULL
• If pipelineBinaryCount is not 0, and pPipelineBinaries is not NULL, pPipelineBinaries must be a valid pointer to an array of pipelineBinaryCount PipelineBinaryKHR handles

See Also

VK_KHR_pipeline_binary, PipelineBinaryKHR, StructureType, createPipelineBinariesKHR

VkPipelineBinaryDataKHR - Structure specifying data and length of a pipeline binary

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, PipelineBinaryKeysAndDataKHR

VkPipelineBinaryKeysAndDataKHR - Structure specifying arrays of key and data pairs

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, PipelineBinaryCreateInfoKHR, PipelineBinaryDataKHR, PipelineBinaryKeyKHR

VkPipelineBinaryKeyKHR - Structure specifying a key to a pipeline binary

Description

Any returned values beyond the first keySize bytes are undefined. Implementations must return a keySize greater than 0, and less-or-equal to MAX_PIPELINE_BINARY_KEY_SIZE_KHR.

Two keys are considered equal if keySize is equal and the first keySize bytes of key compare equal.

Implementations may return a different keySize for different binaries.

Implementations should ensure that keySize is large enough to uniquely identify a pipeline binary.

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, PipelineBinaryKeysAndDataKHR, StructureType, getPipelineBinaryDataKHR, getPipelineKeyKHR

VkPipelineBinaryInfoKHR - Structure specifying pipeline binaries to use during pipeline creation

Description

If a PipelineBinaryInfoKHR structure with a binaryCount greater than 0 is included in the pNext chain of any Vk*PipelineCreateInfo structure when creating a pipeline, implementations must use the data in pPipelineBinaries instead of recalculating it. Any shader module identifiers or shader modules declared in PipelineShaderStageCreateInfo instances are ignored.

If this structure is not included in the pNext chain, it is equivalent to specifying this structure with a binaryCount of 0.

Valid Usage

• binaryCount and the order of the elements in pPipelineBinaries must exactly match that returned by createPipelineBinariesKHR for the matching Vk*PipelineCreateInfo structure and its pNext chain, ignoring the presence of the PipelineBinaryInfoKHR structure, the presence of the PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR flag, and absence of any shader module identifiers or shader modules, for the same global pipeline key, from either:

  • PipelineBinaryCreateInfoKHR::pPipelineCreateInfo, or
  • PipelineBinaryCreateInfoKHR::pipeline

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_PIPELINE_BINARY_INFO_KHR

• If binaryCount is not 0, pPipelineBinaries must be a valid pointer to an array of binaryCount valid PipelineBinaryKHR handles

See Also

VK_KHR_pipeline_binary, PipelineBinaryKHR, StructureType

VkReleaseCapturedPipelineDataInfoKHR - Structure specifying a pipeline whose captured data is to be released

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, Pipeline, StructureType, releaseCapturedPipelineDataKHR

VkPipelineBinaryDataInfoKHR - Structure specifying a pipeline binary to retrieve binary data from

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, PipelineBinaryKHR, StructureType, getPipelineBinaryDataKHR

VkPipelineCreateInfoKHR - Structure specifying a pipeline createinfo chain

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, PipelineBinaryCreateInfoKHR, StructureType, getPipelineKeyKHR

VkPhysicalDevicePipelineBinaryFeaturesKHR - Structure describing support for pipeline binaries

Members

This structure describes the following feature:

Description

If the PhysicalDevicePipelineBinaryFeaturesKHR structure is included in the pNext chain of the PhysicalDeviceFeatures2 structure passed to getPhysicalDeviceFeatures2, it is filled in to indicate whether each corresponding feature is supported. PhysicalDevicePipelineBinaryFeaturesKHR can also be used in the pNext chain of DeviceCreateInfo to selectively enable these features.

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, Bool32, StructureType

VkDevicePipelineBinaryInternalCacheControlKHR - Structure specifying parameter to disable the internal pipeline cache

Description

If the DeviceCreateInfo::pNext chain does not include this structure, then disableInternalCache defaults to FALSE.

Valid Usage

• If PhysicalDevicePipelineBinaryPropertiesKHR::pipelineBinaryInternalCacheControl is FALSE, disableInternalCache must be FALSE

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_DEVICE_PIPELINE_BINARY_INTERNAL_CACHE_CONTROL_KHR

See Also

VK_KHR_pipeline_binary, Bool32, StructureType

VkPhysicalDevicePipelineBinaryPropertiesKHR - Structure describing properties about the pipeline binary implementation

Description

These properties tend to be platform specific and may change depending on external configuration which is outside the scope of this specification. These properties are intended to guide applications when implementations have dedicated caching solutions available. In particular, if the pipelineBinaryPrefersInternalCache limit is exposed, relying on the internal cache may provide some advantage compared to an application-specific solution. An application with its own dedicated solution may still use its own caching system even with this limit exposed.

If the PhysicalDevicePipelineBinaryPropertiesKHR structure is included in the pNext chain of the PhysicalDeviceProperties2 structure passed to getPhysicalDeviceProperties2, it is filled in with each corresponding implementation-dependent property.

Valid Usage (Implicit)

See Also

VK_KHR_pipeline_binary, Bool32, StructureType

VkPipelineBinaryKHR - Opaque handle to a pipeline binary object

See Also

VK_DEFINE_NON_DISPATCHABLE_HANDLE, VK_KHR_pipeline_binary, PipelineBinaryDataInfoKHR, PipelineBinaryHandlesInfoKHR, PipelineBinaryInfoKHR, destroyPipelineBinaryKHR

VkPipelineCreateFlagBits2KHR - Bitmask controlling how a pipeline is created

Description

• PIPELINE_CREATE_2_DISABLE_OPTIMIZATION_BIT_KHR specifies that the created pipeline will not be optimized. Using this flag may reduce the time taken to create the pipeline.

• PIPELINE_CREATE_2_ALLOW_DERIVATIVES_BIT_KHR specifies that the pipeline to be created is allowed to be the parent of a pipeline that will be created in a subsequent pipeline creation call.
• PIPELINE_CREATE_2_DERIVATIVE_BIT_KHR specifies that the pipeline to be created will be a child of a previously created parent pipeline.
• PIPELINE_CREATE_2_VIEW_INDEX_FROM_DEVICE_INDEX_BIT_KHR specifies that any shader input variables decorated as ViewIndex will be assigned values as if they were decorated as DeviceIndex.
• PIPELINE_CREATE_2_DISPATCH_BASE_BIT_KHR specifies that a compute pipeline can be used with cmdDispatchBase with a non-zero base workgroup.
• PIPELINE_CREATE_2_DEFER_COMPILE_BIT_NV specifies that a pipeline is created with all shaders in the deferred state. Before using the pipeline the application must call compileDeferredNV exactly once on each shader in the pipeline before using the pipeline.
• PIPELINE_CREATE_2_CAPTURE_STATISTICS_BIT_KHR specifies that the shader compiler should capture statistics for the pipeline executables produced by the compile process which can later be retrieved by calling getPipelineExecutableStatisticsKHR. Enabling this flag must not affect the final compiled pipeline but may disable pipeline caching or otherwise affect pipeline creation time.
• PIPELINE_CREATE_2_CAPTURE_INTERNAL_REPRESENTATIONS_BIT_KHR specifies that the shader compiler should capture the internal representations of pipeline executables produced by the compile process which can later be retrieved by calling getPipelineExecutableInternalRepresentationsKHR. Enabling this flag must not affect the final compiled pipeline but may disable pipeline caching or otherwise affect pipeline creation time. When capturing IR from pipelines created with pipeline libraries, there is no guarantee that IR from libraries can be retrieved from the linked pipeline. Applications should retrieve IR from each library, and any linked pipelines, separately.
• PIPELINE_CREATE_2_LIBRARY_BIT_KHR specifies that the pipeline cannot be used directly, and instead defines a pipeline library that can be combined with other pipelines using the PipelineLibraryCreateInfoKHR structure. This is available in ray tracing and graphics pipelines.
• PIPELINE_CREATE_2_RAY_TRACING_NO_NULL_ANY_HIT_SHADERS_BIT_KHR specifies that an any-hit shader will always be present when an any-hit shader would be executed. A NULL any-hit shader is an any-hit shader which is effectively SHADER_UNUSED_KHR, such as from a shader group consisting entirely of zeros.
• PIPELINE_CREATE_2_RAY_TRACING_NO_NULL_CLOSEST_HIT_SHADERS_BIT_KHR specifies that a closest hit shader will always be present when a closest hit shader would be executed. A NULL closest hit shader is a closest hit shader which is effectively SHADER_UNUSED_KHR, such as from a shader group consisting entirely of zeros.
• PIPELINE_CREATE_2_RAY_TRACING_NO_NULL_MISS_SHADERS_BIT_KHR specifies that a miss shader will always be present when a miss shader would be executed. A NULL miss shader is a miss shader which is effectively SHADER_UNUSED_KHR, such as from a shader group consisting entirely of zeros.
• PIPELINE_CREATE_2_RAY_TRACING_NO_NULL_INTERSECTION_SHADERS_BIT_KHR specifies that an intersection shader will always be present when an intersection shader would be executed. A NULL intersection shader is an intersection shader which is effectively SHADER_UNUSED_KHR, such as from a shader group consisting entirely of zeros.
• PIPELINE_CREATE_2_RAY_TRACING_SKIP_TRIANGLES_BIT_KHR specifies that triangle primitives will be skipped during traversal using pipeline trace ray instructions.
• PIPELINE_CREATE_2_RAY_TRACING_SKIP_AABBS_BIT_KHR specifies that AABB primitives will be skipped during traversal using pipeline trace ray instructions.
• PIPELINE_CREATE_2_RAY_TRACING_SHADER_GROUP_HANDLE_CAPTURE_REPLAY_BIT_KHR specifies that the shader group handles can be saved and reused on a subsequent run (e.g. for trace capture and replay).
• PIPELINE_CREATE_2_INDIRECT_BINDABLE_BIT_NV specifies that the pipeline can be used in combination with https://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#device-generated-commands.
• PIPELINE_CREATE_2_INDIRECT_BINDABLE_BIT_EXT specifies that the pipeline can be used in a IndirectExecutionSetEXT.
• PIPELINE_CREATE_2_FAIL_ON_PIPELINE_COMPILE_REQUIRED_BIT_KHR specifies that pipeline creation will fail if a compile is required for creation of a valid Pipeline object; PIPELINE_COMPILE_REQUIRED will be returned by pipeline creation, and the Pipeline will be NULL_HANDLE.
• When creating multiple pipelines, PIPELINE_CREATE_2_EARLY_RETURN_ON_FAILURE_BIT_KHR specifies that control will be returned to the application if any individual pipeline returns a result which is not SUCCESS rather than continuing to create additional pipelines.
• PIPELINE_CREATE_2_RAY_TRACING_ALLOW_MOTION_BIT_NV specifies that the pipeline is allowed to use OpTraceRayMotionNV.
• PIPELINE_CREATE_2_RENDERING_FRAGMENT_SHADING_RATE_ATTACHMENT_BIT_KHR specifies that the pipeline will be used with a fragment shading rate attachment.
• PIPELINE_CREATE_2_RENDERING_FRAGMENT_DENSITY_MAP_ATTACHMENT_BIT_EXT specifies that the pipeline will be used with a fragment density map attachment.
• PIPELINE_CREATE_2_LINK_TIME_OPTIMIZATION_BIT_EXT specifies that pipeline libraries being linked into this library should have link time optimizations applied. If this bit is omitted, implementations should instead perform linking as rapidly as possible.
• PIPELINE_CREATE_2_RETAIN_LINK_TIME_OPTIMIZATION_INFO_BIT_EXT specifies that pipeline libraries should retain any information necessary to later perform an optimal link with PIPELINE_CREATE_2_LINK_TIME_OPTIMIZATION_BIT_EXT.
• PIPELINE_CREATE_2_DESCRIPTOR_BUFFER_BIT_EXT specifies that a pipeline will be used with descriptor buffers, rather than descriptor sets.
• PIPELINE_CREATE_2_COLOR_ATTACHMENT_FEEDBACK_LOOP_BIT_EXT specifies that the pipeline may be used with an attachment feedback loop including color attachments.
• PIPELINE_CREATE_2_DEPTH_STENCIL_ATTACHMENT_FEEDBACK_LOOP_BIT_EXT specifies that the pipeline may be used with an attachment feedback loop including depth-stencil attachments.
• PIPELINE_CREATE_2_RAY_TRACING_OPACITY_MICROMAP_BIT_EXT specifies that the ray tracing pipeline can be used with acceleration structures which reference an opacity micromap array.
• PIPELINE_CREATE_2_RAY_TRACING_DISPLACEMENT_MICROMAP_BIT_NV specifies that the ray tracing pipeline can be used with acceleration structures which reference a displacement micromap array.
• PIPELINE_CREATE_2_NO_PROTECTED_ACCESS_BIT_EXT specifies that the pipeline must not be bound to a protected command buffer.
• PIPELINE_CREATE_2_PROTECTED_ACCESS_ONLY_BIT_EXT specifies that the pipeline must not be bound to an unprotected command buffer.
• PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR specifies that PipelineBinaryKHR objects can be created from the pipeline. If PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR is used, implementations should not store pipeline data to an internal cache, if such a cache exists as stated by pipelineBinaryInternalCache. If pipelineBinaryPrefersInternalCache is TRUE, applications should not use PIPELINE_CREATE_2_CAPTURE_DATA_BIT_KHR.
• PIPELINE_CREATE_2_ENABLE_LEGACY_DITHERING_BIT_EXT specifies that the pipeline will be used in a render pass that is begun with RENDERING_ENABLE_LEGACY_DITHERING_BIT_EXT.
• PIPELINE_CREATE_2_EXECUTION_GRAPH_BIT_AMDX specifies that the pipeline will be used in an execution graph

It is valid to set both PIPELINE_CREATE_2_ALLOW_DERIVATIVES_BIT_KHR and PIPELINE_CREATE_2_DERIVATIVE_BIT_KHR. This allows a pipeline to be both a parent and possibly a child in a pipeline hierarchy. See Pipeline Derivatives for more information.

When an implementation is looking up a pipeline in a pipeline cache, if that pipeline is being created using linked libraries, implementations should always return an equivalent pipeline created with PIPELINE_CREATE_2_LINK_TIME_OPTIMIZATION_BIT_EXT if available, whether or not that bit was specified.

Using PIPELINE_CREATE_2_LINK_TIME_OPTIMIZATION_BIT_EXT (or not) when linking pipeline libraries is intended as a performance tradeoff between host and device. If the bit is omitted, linking should be faster and produce a pipeline more rapidly, but performance of the pipeline on the target device may be reduced. If the bit is included, linking may be slower but should produce a pipeline with device performance comparable to a monolithically created pipeline. Using both options can allow latency-sensitive applications to generate a suboptimal but usable pipeline quickly, and then perform an optimal link in the background, substituting the result for the suboptimally linked pipeline as soon as it is available.

See Also

VK_KHR_maintenance5, PipelineCreateFlags2KHR

VK_MAX_PIPELINE_BINARY_KEY_SIZE_KHR - Maximum length of binary key

See Also

VK_KHR_pipeline_binary