Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[vulkan-memory-allocator] update to v3.1.0 #38971

Closed
matthew-rister opened this issue May 28, 2024 · 0 comments · Fixed by #38978
Closed

[vulkan-memory-allocator] update to v3.1.0 #38971

matthew-rister opened this issue May 28, 2024 · 0 comments · Fixed by #38978
Assignees
@LilyWangLL
Labels
category:port-update The issue is with a library, which is requesting update new revision

Comments

@matthew-rister
Copy link

Library name

Vulkan Memory Allocator

New version number

v3.1.0

Other information that may be useful (release notes, etc...)

v3.1.0

This release gathers fixes and improvements made during many months of continuous development on the main branch, mostly based on issues and pull requests on GitHub.

Additions to the library API:

  • Added convenience functions vmaCopyMemoryToAllocation, vmaCopyAllocationToMemory.
  • Added functions vmaCreateAliasingBuffer2, vmaCreateAliasingImage2 that offer creating a buffer/image in an existing allocation with additional allocationLocalOffset.
  • Added function vmaGetAllocationInfo2, structure VmaAllocationInfo2 that return additional information about an allocation, useful for interop with other APIs (#383, #340).
  • Added callback VmaDefragmentationInfo::pfnBreakCallback that allows breaking long execution of vmaBeginDefragmentation.
    Also added PFN_vmaCheckDefragmentationBreakFunction, VmaDefragmentationInfo::pBreakCallbackUserData.
  • Added support for VK_KHR_maintenance4 extension - VMA_ALLOCATOR_CREATE_KHR_MAINTENANCE4_BIT flag (#397).
  • Added support for VK_KHR_maintenance5 extension - VMA_ALLOCATOR_CREATE_KHR_MAINTENANCE5_BIT flag (#411).

Other changes:

  • Changes in debug and configuration macros:
    • Split macros into separate VMA_DEBUG_LOG and VMA_DEBUG_LOG_FORMAT (#297).
    • Added macros VMA_ASSERT_LEAK, VMA_LEAK_LOG_FORMAT separate from normal VMA_ASSERT, VMA_DEBUG_LOG_FORMAT (#379, #385).
    • Added macro VMA_EXTENDS_VK_STRUCT (#347).
  • Countless bug fixes and improvements in the code and documentation, mostly to improve compatibility with various compilers and GPUs, including:
    • Fixed missing #include that resulted in compilation error about snprintf not declared on some compilers (#312).
    • Fixed main memory type selection algorithm for GPUs that have no HOST_CACHED memory type, like Raspberry Pi (#362).
  • Major changes in Cmake script.
  • Fixes in GpuMemDumpVis.py script.
@matthew-rister matthew-rister added the category:port-update The issue is with a library, which is requesting update new revision label May 28, 2024
@Cheney-W Cheney-W mentioned this issue May 28, 2024
Merged
7 tasks
vicroms pushed a commit that referenced this issue May 29, 2024
@Cheney-W
[vulkan-memory-allocator] update to v3.1.0 (#38978)
eb07416 
Fixes #38971

Fixes the path of the config file.
No feature needs to be tested.

- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [x] SHA512s are updated for each updated download.
- [ ] ~The "supports" clause reflects platforms that may be fixed by
this new version.~
- [ ] ~Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.~
- [ ] ~Any patches that are no longer applied are deleted from the
port's directory.~
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LilyWangLL LilyWangLL

Labels
category:port-update The issue is with a library, which is requesting update new revision
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[vulkan-memory-allocator] update to v3.1.0 Cheney-W/vcpkg
2 participants
@matthew-rister @LilyWangLL