Vulkan: More memory barrier simplification and fixes #19017
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
…me rendering errors on NV.
hrydgard
force-pushed
the
more-vulkan-barrier-stuff
branch
from
2c43f38
to
7769bf0
Compare
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.
This cleans up some of the barrier code a bit, and as a side effect fixes a strange rendering error seen on the latest generation NVIDIA cards. (3e91095).
(Also snuck in a change that points README and issue templates to the new buildbot)
This might add a few barriers where we previously didn't had any, but I'm not sure it will actually, and we're now better at merging them anyway, so hopefully there won't be a performance impact.