zero-copy metal backend #35
Closed
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
birkskyum
force-pushed
the
work-on-drawables
branch
from
dfcb00b to
706948f
Compare
birkskyum
force-pushed
the
work-on-drawables
branch
from
d5183c8 to
b9dd86f
Compare
Member
Author
|
Closed in favor of a wgpu integration, now that this is in: |
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 PR introduces a zero-copy metal backend.
A lot of code is reused from:
To get this working, I commented out/removed the CPU image copy path.
Screen.Recording.2025-08-30.at.05.04.21.mov
Some of the solutions used here, won't work with Vulkan. To get an optimized vulkan path, we'll need:
And used the wgpu integration: