Safe Haskell | None |
---|---|
Language | Haskell2010 |
Name
VK_KHR_workgroup_memory_explicit_layout - device extension
VK_KHR_workgroup_memory_explicit_layout
- Name String
VK_KHR_workgroup_memory_explicit_layout
- Extension Type
- Device extension
- Registered Extension Number
- 337
- Revision
- 1
- Extension and Version Dependencies
- Requires Vulkan 1.0
- Requires
VK_KHR_get_physical_device_properties2
- Contact
- Caio Marcelo de Oliveira Filho https://github.com/KhronosGroup/Vulkan-Docs/issues/new?title=VK_KHR_workgroup_memory_explicit_layout:%20&body=@cmarcelo%20
Other Extension Metadata
- Last Modified Date
- 2020-06-01
- IP Status
- No known IP claims.
- Interactions and External Dependencies
- This extension requires SPV_KHR_workgroup_memory_explicit_layout
- Contributors
- Caio Marcelo de Oliveira Filho, Intel
- Jeff Bolz, NVIDIA
- Graeme Leese, Broadcom
- Jason Ekstrand, Intel
- Daniel Koch, NVIDIA
Description
This extension adds Vulkan support for the
SPV_KHR_workgroup_memory_explicit_layout
SPIR-V extension, which allows shaders to explicitly define the layout
of Workgroup
storage class memory and create aliases between variables
from that storage class in a compute shader.
The aliasing feature allows different "views" on the same data, so the shader can bulk copy data from another storage class using one type (e.g. an array of large vectors), and then use the data with a more specific type. It also enables reducing the amount of workgroup memory consumed by allowing the shader to alias data whose lifetimes don’t overlap.
The explicit layout support and some form of aliasing is also required for layering OpenCL on top of Vulkan.
New Structures
Extending
PhysicalDeviceFeatures2
,DeviceCreateInfo
:
New Enum Constants
New SPIR-V Capabilities
Version History
Revision 1, 2020-06-01 (Caio Marcelo de Oliveira Filho)
- Initial version
See Also
PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR
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.
Synopsis
- data PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR = PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR {}
- type KHR_WORKGROUP_MEMORY_EXPLICIT_LAYOUT_SPEC_VERSION = 1
- pattern KHR_WORKGROUP_MEMORY_EXPLICIT_LAYOUT_SPEC_VERSION :: forall a. Integral a => a
- type KHR_WORKGROUP_MEMORY_EXPLICIT_LAYOUT_EXTENSION_NAME = "VK_KHR_workgroup_memory_explicit_layout"
- pattern KHR_WORKGROUP_MEMORY_EXPLICIT_LAYOUT_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a
Documentation
data PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR Source #
VkPhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR - Structure describing the workgroup storage explicit layout features that can be supported by an implementation
Members
The members of the
PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR
structure
describe the following features:
Description
If the PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR
structure is included in the pNext
chain of
PhysicalDeviceFeatures2
,
it is filled with values indicating whether the feature is supported.
PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR
can also be
included in the pNext
chain of DeviceCreateInfo
to enable the feature.
Valid Usage (Implicit)
See Also
PhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR | |
|
Instances
pattern KHR_WORKGROUP_MEMORY_EXPLICIT_LAYOUT_SPEC_VERSION :: forall a. Integral a => a Source #
type KHR_WORKGROUP_MEMORY_EXPLICIT_LAYOUT_EXTENSION_NAME = "VK_KHR_workgroup_memory_explicit_layout" Source #
pattern KHR_WORKGROUP_MEMORY_EXPLICIT_LAYOUT_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a Source #