Use associated physical device from custom instance
authorAri Suonpaa <ari.suonpaa@siru.fi>
Tue, 29 Mar 2022 08:56:44 +0000 (11:56 +0300)
committerMatthew Netsch <quic_mnetsch@quicinc.com>
Thu, 7 Apr 2022 17:47:58 +0000 (17:47 +0000)
commit78bde8057e3caf6bb4e1742a9a75dabb94d04a9a
tree2062de4f0826f3a9f243b6be2daee1f97760a26d
parent337453b58a8fd3308ff33360e4f879067ae779b4
Use associated physical device from custom instance

Some of the API feature info tests created a custom instance,
but still used the default physical device. This is fixed by
choosing a physical device using the custom instance.

Comparison of VkPhysicalDeviceMemoryProperties was also
changed to only check the active memoryTypes and memoryHeaps
array elements instead of doing one large deMemCmp.

VK-GL-CTS Issue: 3590

Affects:

dEQP-VK.api.info.*

Components: Vulkan
Change-Id: I2378bcd1e97b7f85e533d34c5b5f6ac3e4fa9b93
external/vulkancts/modules/vulkan/api/vktApiFeatureInfo.cpp