VkPhysicalDevice should use Instance allocation scope

Physical device was using the wrong allocations scope. Tests: dEQP-VK.wsi.xlib.surface.create_custom_allocator Tests: dEQP-VK.wsi.xlib.surface.create_simulate_oom Bug: b/132451407 Change-Id: I242d97548bdf01cbdab5cc708469bca02a845a66 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/31691 Presubmit-Ready: Ben Clayton <bclayton@google.com> Reviewed-by: Chris Forbes <chrisforbes@google.com> Tested-by: Hernan Liatis <hliatis@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

VkPhysicalDevice should use Instance allocation scope
94e3e4ac · Hernan Liatis · 35993b26 · 94e3e4ac
Commit 94e3e4ac authored May 17, 2019 by Hernan Liatis
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

VkPhysicalDevice.hpp src/Vulkan/VkPhysicalDevice.hpp +1 -1

No files found.
--- a/src/Vulkan/VkPhysicalDevice.hpp
+++ b/src/Vulkan/VkPhysicalDevice.hpp
@@ -27,7 +27,7 @@ namespace vk
 class PhysicalDevice
 {
 public:
-	static constexpr VkSystemAllocationScope GetAllocationScope() { return VK_SYSTEM_ALLOCATION_SCOPE_DEVICE; }
+	static constexpr VkSystemAllocationScope GetAllocationScope() { return VK_SYSTEM_ALLOCATION_SCOPE_INSTANCE; }
 	PhysicalDevice(const void*, void* mem);
 	void destroy(const VkAllocationCallbacks* pAllocator) {}