Vulkan 1.4.347 made its debut overnight as the latest routine update to this high performance graphics and compute API. Beyond the usual maintenance churn over the past week, Vulkan 1.4.347 brings three new extensions.
The new extensions releasing with Vulkan 1.4.347 include VK_KHR_device_fault, VK_KHR_shader_abort, and VK_KHR_shader_constant_data.
VK_KHR_device_fault was worked on by engineers at many different companies. The VK_KHR_device_fault extension adds new commands of vkGetDeviceFaultReportsKHR and vkGetDeviceFaultDebugInfoKHR. With the vkGetDeviceFaultReportsKHR command when a GPU device loss/fault occurs you can obtain more information on the possible cause of the GPU fault(s) and to generate a binary crash dump that can then be externally analyzed. The vkGetDeviceFaultDebugInfoKHR command provides another interface for providing extended GPU vendor-specific crash post-mortem information. VK_KHR_device_fault was worked on by Vulkan working group members over the past two years and is now ready with Vulkan 1.4.347.
VK_KHR_shader_abort was worked on by AMD, NVIDIA, Samsung, ARM, and Imagination for enabling the use of the “OpAbortKHR” instruction in shaders for aborting.
Lastly, the VK_KHR_shader_constant_data extension allows applications to specify large constant data arrays in their shaders. This VK_KHR_shader_constant_data extension is part of an effort to provide better string support to the Vulkan API.
More details on these new extensions and other changes with Vulkan 1.4.347 can be found via Vulkan-Docs on GitHub.
