C Specification

The VkTensorViewCreateInfoARM structure is defined as:

// Provided by VK_ARM_tensors
typedef struct VkTensorViewCreateInfoARM {
    VkStructureType               sType;
    const void*                   pNext;
    VkTensorViewCreateFlagsARM    flags;
    VkTensorARM                   tensor;
    VkFormat                      format;
} VkTensorViewCreateInfoARM;

Members

  • sType is a VkStructureType value identifying this structure.

  • pNext is NULL or a pointer to a structure extending this structure.

  • flags is reserved for future use.

  • tensor is a VkTensorARM on which the view will be created.

  • format is a VkFormat describing the format and type used to interpret elements in the tensor.

Description

If tensor was created with the VK_TENSOR_CREATE_MUTABLE_FORMAT_BIT_ARM flag, format can be different from the tensor’s format, but if they are not equal they must be compatible. Tensor format compatibility is defined in the Format Compatibility Classes section. Views of compatible formats will have the same mapping between element locations irrespective of the format, with only the interpretation of the bit pattern changing.

Note

Values intended to be used with one view format may not be exactly preserved when written or read through a different format. For example, an integer value that happens to have the bit pattern of a floating-point denorm or NaN may be flushed or canonicalized when written or read through a view with a floating-point format. Similarly, a value written through a signed normalized format that has a bit pattern exactly equal to -2b may be changed to -2b + 1 as described in Conversion from Normalized Fixed-Point to Floating-Point.

Valid Usage
  • VUID-VkTensorViewCreateInfoARM-tensor-09743
    If tensor was not created with VK_TENSOR_CREATE_MUTABLE_FORMAT_BIT_ARM flag, format must be identical to the format used to create tensor

  • VUID-VkTensorViewCreateInfoARM-tensor-09744
    If tensor was created with VK_TENSOR_CREATE_MUTABLE_FORMAT_BIT_ARM flag, format must be compatible with the format used to create tensor, as defined in Format Compatibility Classes

  • VUID-VkTensorViewCreateInfoARM-flags-09745
    If flags includes VK_TENSOR_VIEW_CREATE_DESCRIPTOR_BUFFER_CAPTURE_REPLAY_BIT_ARM, the descriptorBufferCaptureReplay feature must be enabled

  • VUID-VkTensorViewCreateInfoARM-pNext-09746
    If the pNext chain includes a VkOpaqueCaptureDescriptorDataCreateInfoEXT structure, flags must contain VK_TENSOR_VIEW_CREATE_DESCRIPTOR_BUFFER_CAPTURE_REPLAY_BIT_ARM

  • VUID-VkTensorViewCreateInfoARM-usage-09747
    The usage flags of tensor must have at least one of the following bits set:

    • VK_TENSOR_USAGE_SHADER_BIT_ARM

    • VK_TENSOR_USAGE_DATA_GRAPH_BIT_ARM

  • VUID-VkTensorViewCreateInfoARM-usage-09748
    The tensor view’s format features must contain the format feature flags required by the usage flags of tensor for format as indicated in the https://registry.khronos.org/vulkan/specs/latest/html/vkspec.html#format-feature-dependent-usage-flags section

  • VUID-VkTensorViewCreateInfoARM-tensor-09749
    If tensor is non-sparse then it must be bound completely and contiguously to a single VkDeviceMemory object

Valid Usage (Implicit)
  • VUID-VkTensorViewCreateInfoARM-sType-sType
    sType must be VK_STRUCTURE_TYPE_TENSOR_VIEW_CREATE_INFO_ARM

  • VUID-VkTensorViewCreateInfoARM-pNext-pNext
    pNext must be NULL or a pointer to a valid instance of VkOpaqueCaptureDescriptorDataCreateInfoEXT

  • VUID-VkTensorViewCreateInfoARM-sType-unique
    The sType value of each structure in the pNext chain must be unique

  • VUID-VkTensorViewCreateInfoARM-flags-parameter
    flags must be a valid combination of VkTensorViewCreateFlagBitsARM values

  • VUID-VkTensorViewCreateInfoARM-tensor-parameter
    tensor must be a valid VkTensorARM handle

  • VUID-VkTensorViewCreateInfoARM-format-parameter
    format must be a valid VkFormat value

See Also

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 2014-2025 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0