This repository was archived by the owner on Feb 25, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6k
[Impeller] Add RAII wrappers for VMA objects. #43626
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,6 +13,7 @@ | |
#include "impeller/renderer/backend/vulkan/device_holder.h" | ||
#include "impeller/renderer/backend/vulkan/vk.h" | ||
|
||
#include <array> | ||
#include <memory> | ||
|
||
namespace impeller { | ||
|
@@ -28,8 +29,8 @@ class AllocatorVK final : public Allocator { | |
static constexpr size_t kPoolCount = 3; | ||
|
||
fml::RefPtr<vulkan::VulkanProcTable> vk_; | ||
VmaAllocator allocator_ = {}; | ||
VmaPool staging_buffer_pools_[kPoolCount] = {}; | ||
UniqueAllocatorVMA allocator_; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So, to state the obvious as I'm still a C++ noob: The RAII wrappers handle destroying the native resources, and we always go though destructors in reverse order. So staging_buffer_pools_ being declared after allocator_ ensures that we destroy the pools with the allocator before destroying the allocator itself? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right. |
||
std::array<UniquePoolVMA, kPoolCount> staging_buffer_pools_; | ||
std::weak_ptr<Context> context_; | ||
std::weak_ptr<DeviceHolder> device_holder_; | ||
ISize max_texture_size_; | ||
|
@@ -66,8 +67,6 @@ class AllocatorVK final : public Allocator { | |
// |Allocator| | ||
ISize GetMaxTextureSizeSupported() const override; | ||
|
||
static bool CreateBufferPool(VmaAllocator allocator, VmaPool* pool); | ||
|
||
FML_DISALLOW_COPY_AND_ASSIGN(AllocatorVK); | ||
}; | ||
|
||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The image view is already a unique object. It had to be reset manually earlier because the image was explicitly collected. With the RAII wrapper, there is no need as the ivar destruction order holds.