zink: Correct compiler issue with have_moltenvk member having been moved.
authorDuncan Hopkins <duncan@duncanhopkins.me.uk>
Thu, 3 Jun 2021 13:07:29 +0000 (14:07 +0100)
committerMarge Bot <eric+marge@anholt.net>
Fri, 4 Jun 2021 08:58:16 +0000 (08:58 +0000)
have_moltenvk was moved to a different location but code being protected in platform specific guard, so was unnoticed.

Fixes: 598dc3dca41 ("zink: use cached memory for all resources when possible")

Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11129>

src/gallium/drivers/zink/zink_resource.c

index 4a82acf..60db3c8 100644 (file)
@@ -973,7 +973,7 @@ buffer_transfer_map(struct zink_context *ctx, struct zink_resource *res, unsigne
       // This is a known limitation of MoltenVK.
       // See https://github.com/KhronosGroup/MoltenVK/blob/master/Docs/MoltenVK_Runtime_UserGuide.md#known-moltenvk-limitations
 
-       || screen->have_moltenvk
+       || screen->instance_info.have_MVK_moltenvk
 #endif
       ) {
       VkDeviceSize size = box->width;