Fix for getPhysicalDeviceFeatures2 loader issue
authorMarcin Rogucki <marcin.rogucki@mobica.com>
Mon, 20 Nov 2017 15:44:51 +0000 (16:44 +0100)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Thu, 14 Dec 2017 09:35:56 +0000 (04:35 -0500)
commitb68af198a76622bebeb81d0ae0fe007c6527d35e
tree883417194672c40ec247046b8cec8148a6ed4d23
parentd6b9480d2d7bc67d7ef9522f001f1367f08fbaea
Fix for getPhysicalDeviceFeatures2 loader issue

For all instance methods taking VkPhysicalDevice
as a first parameter that were moved to core in
1.1 there is now a dynamic dispatch based on
physical device api version. If version is 1.1 or
above a core method is used. If version is lower
than that a counterpart extension method is used.

Additionally a pre-instance is created to enumerate
all physical devices and select lowest version to
be able to enable proper extensions set for final
instance.

Components: Vulkan

VK-GL-CTS issue: 854

Affects: All tests using getPhysicalDeviceFeatures2

Change-Id: Ia68a5cac23ae35566fcf99bc56c93c9cb77f33e0
external/vulkancts/framework/vulkan/vkInitInstanceFunctionPointers.inl
external/vulkancts/framework/vulkan/vkInstanceDriverImpl.inl
external/vulkancts/framework/vulkan/vkInstanceFunctionPointers.inl
external/vulkancts/modules/vulkan/api/vktApiVersionCheck.cpp
external/vulkancts/modules/vulkan/vktTestCase.cpp
external/vulkancts/modules/vulkan/vktTestCase.hpp
external/vulkancts/scripts/gen_framework.py