Use canonical antono2.memory dependency - #10
Merged
Conversation
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.
Migrates policy imports to antono2.memory and pins v1.0.2, while keeping the public Vulkan API independent through UploadRingStats. Adds reference-counted block-level mapping so multiple shared staging suballocations can remain mapped concurrently. CI checks out the dependency at its canonical nested module path.\n\nValidated with V 0.5.2: formatting, vetting, all unit tests, GCC debug/production builds, documentation generation, the real Lavapipe Vulkan smoke example, and visible v_vulkan_video playback on an NVIDIA GTX 1060. This PR should merge after antono2.memory is registered on VPM.