FFE: update vulkan to 1.2.135
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glslang (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
spirv-headers (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
spirv-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
vulkan-loader (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
vulkan-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
vulkan-validationlayers (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Upstream doesn't provide release notes, vulkan tags follow the SDK releases so this is probably closest to reality:
https:/
snippet copied here:
<--
Overview of new features to Vulkan SDK 1.2.135
Inclusion of the shader tool chain API libraries coming from glslang, shaderc, SPIRV-Cross, and SPIRV-Tools.
A new validation layer object has been added that processes debugPrintfEXT operations in shaders, retrieves the values to be printed, and sends a formatted string to the validation debug callback.
Easier and quicker to build samples.
Enhancements to Best Practices in the Khronos Validation Layer including ARM GPU-specific best practices checks.
Support for the following many new extensions including new provisional VK_KHR_ray_tracing.
Added support for VK_EXT_tooling_info for several LunarG SDK layers.
VK_
Some notable improvements to Validation Layer error messages in response to feedback from the recent LunarG Vulkan Ecosystem Survey.
Bug fixes and improved validation coverage.
-->
risk:
vulkan-loader - very low, the loader library / headers is just the plumbing for the actual drivers to support the new feature(s)
vulkan-tools - fixes for vulkaninfo, no risk really
vulkan-
spirv/glslang - updates are required by vulkan-
testing:
these have been in debian for a week now without issues, and seem fine on focal too, vkcube/vulkaninfo work like before
Please give us some more information to be able to judge this freeze exception request.
Like, what's the risk / impact, what testing have you done? Why do we need this feature in 20.04?
I'm going to reject the pending packages in the queue for now. If approved they can be re-synced.