Bug#1021201: marked as done (vulkan-loader: new upstream stable point release 1.3.224.1)
Your message dated Tue, 4 Oct 2022 14:36:54 +0100
with message-id <Yzw29rf+f2SBwke8@momentum.pseudorandom.co.uk>
and subject line Re: Bug#1021201: vulkan-loader: new upstream stable point release 1.3.224.1
has caused the Debian Bug report #1021201,
regarding vulkan-loader: new upstream stable point release 1.3.224.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1021201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021201
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan-loader
Version: 1.3.224.0-1
Severity: wishlist
vulkan-loader is currently at upstream version 1.3.224.0, but upstream's
sdk-1.3.224 stable branch now has a 1.3.224.1 point release with these
release notes:
> Enable layer interception of unknown functions
>
> Re-add previously reverted behavior that allows layers to setup
> dispatch chains for unknown physical device and device functions during
> vkCreateInstance. Previously, functions not known to the loader could
> not be queried by a layer during vkCreateInstance (when dispatch tables
> should be setup). The change adds support for unknown functions in the
> trampolines of vkGetInstanceProcAddr and vkGetPhysicalDeviceProcAddr.
If I'm reading correctly, this is a backport of part of
https://github.com/KhronosGroup/Vulkan-Loader/pull/999,
which seems to be a fix for bugs seen with the RenderDoc and
GFXReconstruct development tools.
smcv
--- End Message ---
--- Begin Message ---
On Tue, 04 Oct 2022 at 16:08:25 +0300, Timo Aaltonen wrote:
> Only vulkan-validationlayers had actual changes in .1, -loader is unchanged
Sorry for the noise, I hadn't spotted that the change I was asking about
is already in sdk-1.3.224.0 (it is the difference between v1.3.224 and
sdk-1.3.224.0 in upstream's git repo).
smcv
--- End Message ---
Reply to: