Cache resource sizes in multiples of alignment. #423
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
github-actions
bot
added
Build
bbernhar
force-pushed
the
cache
branch
2 times, most recently
from
77c4817 to
f15e964
Compare
bbernhar
force-pushed
the
cache
branch
2 times, most recently
from
f91f78c to
ca9e5e2
Compare
bbernhar
changed the title
github-actions
bot
added
the
Frontend
bbernhar
force-pushed
the
cache
branch
2 times, most recently
from
44d2ad6 to
41753db
Compare
Previously, the size-cache was limited to powers-of-two. This change also includes page-multiples. For example, {4k, 8k, 12k} vs {4k, 8k, 16k}.
Since the size-cache was intended to be always enabled, the build option default was reversed from enable => disable.
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.
Previously, the size-cache was limited to powers-of-two. This change also includes page-multiples. For example, {4k, 8k, 12k} vs {4k, 8k, 16k}.
Since the size-cache was intended to be always enabled, the build option default was reversed from enable => disable.