runtime: Add a basic monomorphic cache implementation#24
Draft
runtime: Add a basic monomorphic cache implementation#24
Conversation
This is a very naive implementation that has the following issues; - It over-allocates by a lot, and I mean *a lot*. It allocates two words even when the instruction isn't a message send. - Currently the memory is owned by the global actor, but who really owns the memory is kinda dubious. When do the writes to the inline cache happen? Should we record actor-owned objects on a global object's inline cache? There are still many questions to be answered, but this should be a good MVP.
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.
Tasks:
ExecutableMapOptional tasks:
Questions to answer:
ArrayObjector should it be given its own dedicated object type?