You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This loop is only looking for image views derived from the image being destroyed, so this is inefficient, and additionally causes spurious dependencies from vkDestroyImage to every image view (and hence every image).
The text was updated successfully, but these errors were encountered:
This means vkDestroyImage no longer needs to loop over all image views to find
the views of the image being destroyed.
This change breaks compatibility with old captures.
Fixesgoogle#2457
bjoeris
added a commit
to bjoeris/gapid
that referenced
this issue
Dec 14, 2018
This means vkDestroyImage no longer needs to loop over all image views to find
the views of the image being destroyed.
This change breaks compatibility with old captures.
Fixesgoogle#2457
This means vkDestroyImage no longer needs to loop over all image views to find
the views of the image being destroyed.
This change breaks compatibility with old captures.
Fixes#2457
This loop is only looking for image views derived from the image being destroyed, so this is inefficient, and additionally causes spurious dependencies from vkDestroyImage to every image view (and hence every image).
The text was updated successfully, but these errors were encountered: