Fix support for VK_KHR_pipeline_binary
#2634
Open
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.
VkPipelineCreateInfoKHRis a particular structure as it can take any kind ofPipelineCreateInfoin itspNextchain, in addition to being required to have a non-nullpNextmember.This was not correctly handled by the generated code because
Vk*PipelineCreateInfostructures don't have thestructextendsflag set in the Vulkan registry. This commit aims at fixing that by blacklisting this structure and writing the encoder/decoders manually.Ideally, this should be solved in the codegen by not considering only structs with the
structextendsflag as possible encounters in apNextchain