Implement basic support for VK_EXT_tooling_info. #2435
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements basic support for
VK_EXT_tooling_info.Everything is wired up for the
MVKPhysicalDeviceto provide tool properties, but it currently just returns that there are no tools, since (as far as I can tell) Metal does not have a standard way of reporting any attached tools on the Metal side of things. However, with support now advertised, applications can now properly detect support and get information on Vulkan-side tools from the Vulkan loader in the middle, such as the Vulkan Validation Layers if attached.Passes both available CTS tests
dEQP-VK.api.tooling_info.validate_getteranddEQP-VK.api.tooling_info.validate_tools_properties.