HORIZON HASKELLDocslts/ghc-10.0.xfc4e5982026-10-11Search names, modules, packages, or :: a typeCtrl K

GHC 10.0.0.20260917 · lts/ghc-10.0.x · fc4e598 · 2026-10-11

Modulevulkan-3.27GHC2021

Vulkan.Extensions.VK_NV_dedicated_allocation_image_aliasing

Name

VK_NV_dedicated_allocation_image_aliasing - device extension

VK_NV_dedicated_allocation_image_aliasing

Name String

VK_NV_dedicated_allocation_image_aliasing

Extension Type

Device extension

Registered Extension Number

241

Revision

1

Ratification Status

Not ratified

Extension and Version Dependencies

VK_KHR_dedicated_allocation      and

VK_KHR_get_physical_device_properties2 or Vulkan Version 1.1

Contact

Other Extension Metadata

Last Modified Date

2019-01-04

Contributors

  • Nuno Subtil, NVIDIA

  • Jeff Bolz, NVIDIA

  • Eric Werness, NVIDIA

  • Axel Gneiting, id Software

Description

This extension allows applications to alias images on dedicated allocations, subject to specific restrictions: the extent and the number of layers in the image being aliased must be smaller than or equal to those of the original image for which the allocation was created, and every other image parameter must match.

New Structures

New Enum Constants

Version History

  • Revision 1, 2019-01-04 (Nuno Subtil)

    • Internal revisions

See Also

No cross-references are available

Document Notes

For more information, see the Vulkan Specification.

This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.

  • 3 types
  • Packagevulkan-3.27
  • Exports5
  • LanguageGHC2021
  • LicenceBSD-3-Clause
  • SourceVK_NV_dedicated_allocation_image_aliasing.hs
datadata PhysicalDeviceDedicatedAllocationImageAliasingFeaturesNV
#

VkPhysicalDeviceDedicatedAllocationImageAliasingFeaturesNV - Structure describing dedicated allocation image aliasing features that can be supported by an implementation

Members

This structure describes the following feature:

Description

If the PhysicalDeviceDedicatedAllocationImageAliasingFeaturesNV 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. If the application wishes to use a Device with any features described by PhysicalDeviceDedicatedAllocationImageAliasingFeaturesNV, it must add an instance of the structure, with the desired feature members set to TRUE, to the pNext chain of DeviceCreateInfo when creating the Device.

Structure Chaining

Extends the structures

See Also

VK_NV_dedicated_allocation_image_aliasing, Bool32, StructureType

Constructors

Instances6Eq, Show, Storable, FromCStruct, ToCStruct, Zero