Move execute program out of vulkan backend#1356
Draft
manon-traverse wants to merge 36 commits into
Draft
Conversation
…d to shared file.
…y are implemented.
…mipmap creation is supported on dx12.
…code. Most tests pass on VK with migration code :D Get vulkan in a working state, apart from features not supported on dx12.
…escriptor table building.
…nt required bind points on vulkan.
…bstraction where needed.
This file contains hidden or 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
1 participant
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.
Based on #1355
executeProgram no longer needs to live in the Vulkan backend. We can use the shared
executeUnitTestfunction, which means we have one code path that handles the unit test side of things, and does the dx12 or vulkan things via the abstraction layer.