blob: 260b73a6b643fff97142e78bc905f11836c14f67 [file] [log] [blame]
// WARNING: DO NOT MODIFY! This file is automatically generated from the vk.xml registry
.Valid Usage (Implicit)
****
* [[VUID-vkAllocateMemory-device-parameter]] pname:device must: be a valid sname:VkDevice handle
* [[VUID-vkAllocateMemory-pAllocateInfo-parameter]] pname:pAllocateInfo must: be a valid pointer to a valid sname:VkMemoryAllocateInfo structure
* [[VUID-vkAllocateMemory-pAllocator-parameter]] If pname:pAllocator is not `NULL`, pname:pAllocator must: be a valid pointer to a valid sname:VkAllocationCallbacks structure
* [[VUID-vkAllocateMemory-pMemory-parameter]] pname:pMemory must: be a valid pointer to a sname:VkDeviceMemory handle
****
.Return Codes
****
ifndef::doctype-manpage[]
<<fundamentals-successcodes,Success>>::
endif::doctype-manpage[]
ifdef::doctype-manpage[]
On success, this command returns::
endif::doctype-manpage[]
* ename:VK_SUCCESS
ifndef::doctype-manpage[]
<<fundamentals-errorcodes,Failure>>::
endif::doctype-manpage[]
ifdef::doctype-manpage[]
On failure, this command returns::
endif::doctype-manpage[]
* ename:VK_ERROR_OUT_OF_HOST_MEMORY
* ename:VK_ERROR_OUT_OF_DEVICE_MEMORY
* ename:VK_ERROR_TOO_MANY_OBJECTS
* ename:VK_ERROR_INVALID_EXTERNAL_HANDLE
****