@@ -1467,17 +1467,17 @@ typedef struct VmaAllocationInfo
14671467typedef struct VmaAllocationInfo2
14681468{
14691469 /** \brief Basic parameters of the allocation.
1470-
1470+
14711471 If you need only these, you can use function vmaGetAllocationInfo() and structure #VmaAllocationInfo instead.
14721472 */
14731473 VmaAllocationInfo allocationInfo;
14741474 /** \brief Size of the `VkDeviceMemory` block that the allocation belongs to.
1475-
1475+
14761476 In case of an allocation with dedicated memory, it will be equal to `allocationInfo.size`.
14771477 */
14781478 VkDeviceSize blockSize;
14791479 /** \brief `VK_TRUE` if the allocation has dedicated memory, `VK_FALSE` if it was placed as part of a larger memory block.
1480-
1480+
14811481 When `VK_TRUE`, it also means `VkMemoryDedicatedAllocateInfo` was used when creating the allocation
14821482 (if VK_KHR_dedicated_allocation extension or Vulkan version >= 1.1 is enabled).
14831483 */
@@ -2567,7 +2567,7 @@ VMA_CALL_PRE VkResult VMA_CALL_POST vmaCreateAliasingBuffer(
25672567\param allocator
25682568\param allocation Allocation that provides memory to be used for binding new buffer to it.
25692569\param allocationLocalOffset Additional offset to be added while binding, relative to the beginning of the allocation. Normally it should be 0.
2570- \param pBufferCreateInfo
2570+ \param pBufferCreateInfo
25712571\param[out] pBuffer Buffer that was created.
25722572
25732573This function automatically:
@@ -6195,7 +6195,7 @@ class VmaWin32Handle
61956195 HANDLE m_hHandle;
61966196 VMA_RW_MUTEX m_Mutex; // Protects access m_Handle
61976197};
6198- #else
6198+ #else
61996199class VmaWin32Handle
62006200{
62016201 // ABI compatibility
@@ -10594,7 +10594,7 @@ VmaDeviceMemoryBlock::VmaDeviceMemoryBlock(VmaAllocator hAllocator)
1059410594 m_hMemory(VK_NULL_HANDLE),
1059510595 m_MapCount(0),
1059610596 m_pMappedData(VMA_NULL),
10597- m_Handle(VMA_NULL ) {}
10597+ m_Handle() {}
1059810598
1059910599VmaDeviceMemoryBlock::~VmaDeviceMemoryBlock()
1060010600{
@@ -16675,7 +16675,7 @@ VMA_CALL_PRE VkResult VMA_CALL_POST vmaGetMemoryWin32Handle(VmaAllocator VMA_NOT
1667516675 VMA_DEBUG_GLOBAL_MUTEX_LOCK;
1667616676 return allocation->GetWin32Handle(allocator, hTargetProcess, pHandle);
1667716677}
16678- #endif // VMA_EXTERNAL_MEMORY_WIN32
16678+ #endif // VMA_EXTERNAL_MEMORY_WIN32
1667916679#endif // VMA_STATS_STRING_ENABLED
1668016680#endif // _VMA_PUBLIC_INTERFACE
1668116681#endif // VMA_IMPLEMENTATION
@@ -18929,7 +18929,7 @@ res = vmaCreateBuffer(g_Allocator, &bufCreateInfo, &allocCreateInfo, &buf, &allo
1892918929vmaDestroyBuffer(g_Allocator, buf, alloc);
1893018930\endcode
1893118931
18932- If you need each allocation to have its own device memory block and start at offset 0, you can still do
18932+ If you need each allocation to have its own device memory block and start at offset 0, you can still do
1893318933by using #VMA_ALLOCATION_CREATE_DEDICATED_MEMORY_BIT flag. It works also with custom pools.
1893418934
1893518935\section vk_khr_external_memory_win32_exporting_win32_handle Exporting Win32 handle
0 commit comments