Safe Haskell | None |
---|---|
Language | Haskell2010 |
Synopsis
- createShaderModule :: forall a io. (Extendss ShaderModuleCreateInfo a, PokeChain a, MonadIO io) => Device -> ShaderModuleCreateInfo a -> ("allocator" ::: Maybe AllocationCallbacks) -> io ShaderModule
- withShaderModule :: forall a io r. (Extendss ShaderModuleCreateInfo a, PokeChain a, MonadIO io) => Device -> ShaderModuleCreateInfo a -> Maybe AllocationCallbacks -> (io ShaderModule -> (ShaderModule -> io ()) -> r) -> r
- destroyShaderModule :: forall io. MonadIO io => Device -> ShaderModule -> ("allocator" ::: Maybe AllocationCallbacks) -> io ()
- data ShaderModuleCreateInfo (es :: [Type]) = ShaderModuleCreateInfo {
- next :: Chain es
- flags :: ShaderModuleCreateFlags
- code :: ByteString
Documentation
:: forall a io. (Extendss ShaderModuleCreateInfo a, PokeChain a, MonadIO io) | |
=> Device |
|
-> ShaderModuleCreateInfo a |
|
-> ("allocator" ::: Maybe AllocationCallbacks) |
|
-> io ShaderModule |
vkCreateShaderModule - Creates a new shader module object
Description
Once a shader module has been created, any entry points it contains can be used in pipeline shader stages as described in Compute Pipelines and Graphics Pipelines.
If the shader stage fails to compile
ERROR_INVALID_SHADER_NV
will be generated
and the compile log will be reported back to the application by
VK_EXT_debug_report
if enabled.
Valid Usage (Implicit)
device
must be a validDevice
handle
pCreateInfo
must be a valid pointer to a validShaderModuleCreateInfo
structure- If
pAllocator
is notNULL
,pAllocator
must be a valid pointer to a validAllocationCallbacks
structure pShaderModule
must be a valid pointer to aShaderModule
handle
Return Codes
See Also
AllocationCallbacks
,
Device
, ShaderModule
,
ShaderModuleCreateInfo
withShaderModule :: forall a io r. (Extendss ShaderModuleCreateInfo a, PokeChain a, MonadIO io) => Device -> ShaderModuleCreateInfo a -> Maybe AllocationCallbacks -> (io ShaderModule -> (ShaderModule -> io ()) -> r) -> r Source #
A convenience wrapper to make a compatible pair of calls to
createShaderModule
and destroyShaderModule
To ensure that destroyShaderModule
is always called: pass
bracket
(or the allocate function from your
favourite resource management library) as the first argument.
To just extract the pair pass (,)
as the first argument.
:: forall io. MonadIO io | |
=> Device |
|
-> ShaderModule |
|
-> ("allocator" ::: Maybe AllocationCallbacks) |
|
-> io () |
vkDestroyShaderModule - Destroy a shader module
Description
A shader module can be destroyed while pipelines created using its shaders are still in use.
Valid Usage
- If
AllocationCallbacks
were provided whenshaderModule
was created, a compatible set of callbacks must be provided here
- If no
AllocationCallbacks
were provided whenshaderModule
was created,pAllocator
must beNULL
Valid Usage (Implicit)
device
must be a validDevice
handle
- If
shaderModule
is notNULL_HANDLE
,shaderModule
must be a validShaderModule
handle - If
pAllocator
is notNULL
,pAllocator
must be a valid pointer to a validAllocationCallbacks
structure - If
shaderModule
is a valid handle, it must have been created, allocated, or retrieved fromdevice
Host Synchronization
- Host access to
shaderModule
must be externally synchronized
See Also
data ShaderModuleCreateInfo (es :: [Type]) Source #
VkShaderModuleCreateInfo - Structure specifying parameters of a newly created shader module
Valid Usage
codeSize
must be greater than 0
- If
pCode
is a pointer to SPIR-V code,codeSize
must be a multiple of 4 pCode
must point to either valid SPIR-V code, formatted and packed as described by the Khronos SPIR-V Specification or valid GLSL code which must be written to theGL_KHR_vulkan_glsl
extension specification- If
pCode
is a pointer to SPIR-V code, that code must adhere to the validation rules described by the Validation Rules within a Module section of the SPIR-V Environment appendix - If
pCode
is a pointer to GLSL code, it must be valid GLSL code written to theGL_KHR_vulkan_glsl
GLSL extension specification pCode
must declare theShader
capability for SPIR-V codepCode
must not declare any capability that is not supported by the API, as described by the Capabilities section of the SPIR-V Environment appendix- If
pCode
declares any of the capabilities listed as optional in the SPIR-V Environment appendix, the corresponding feature(s) must be enabled
Valid Usage (Implicit)
sType
must beSTRUCTURE_TYPE_SHADER_MODULE_CREATE_INFO
pNext
must beNULL
or a pointer to a valid instance ofShaderModuleValidationCacheCreateInfoEXT
- The
sType
value of each struct in thepNext
chain must be unique flags
must be0
pCode
must be a valid pointer to an array of \(\textrm{codeSize} \over 4\)uint32_t
values
See Also
ShaderModuleCreateInfo | |
|