<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - segfault when calling vkGetPhysicalDeviceFormatProperties with VK_FORMAT_PVRTC1_2BPP_UNORM_BLOCK_IMG" href="https://bugs.freedesktop.org/show_bug.cgi?id=101956#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - segfault when calling vkGetPhysicalDeviceFormatProperties with VK_FORMAT_PVRTC1_2BPP_UNORM_BLOCK_IMG" href="https://bugs.freedesktop.org/show_bug.cgi?id=101956">bug 101956</a> from <a class="email" href="mailto:mikes@lunarg.com" title="Mike Schuchardt <mikes@lunarg.com>"> Mike Schuchardt</a> <pre>This patch fixes the reported issue. After more consideration I'm not sure this is a valid use case because of the documented interaction between physical-device-level extension functionality and device extensions. >From the spec 31.2.1, last paragraph: In order to avoid using an instance extension, which often requires loader support, the VK_KHR_get_physical_device_properties2 extension allows physical-device-level extension functionality to be implemented within device extensions (which must depend on the VK_KHR_get_physical_device_properties2 extension). It is further muddled by the fact that VK_IMG_format_pvrtc predates VK_KHR_get_physical_device_properties2, but I believe the intent is the same.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>