Repository navigation
Stack allocator memory optimization - #82
Merged
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
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 implements a stack allocator (linear allocator with rewinding capabilities), used to optimize scenarios where temporary heap memory is necessary.
The scratch is used throughout the whole kitty graphics protocol logic, in OSC52 and during font baking when oversample is turned on.
Changes:
inlinekeyword. That's because every function is either called once or is tiny enough, where the compiler inlining the function doesn't affect the binary size at all.-While rewriting kitty logic, certain parts got optimized:
SFTE_TERM_ALT_SCREENvalue back to 1.