Tagged pointer prototype and ready to run interpreter integration study #2863
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
cshung
added
the
* NO MERGE *
cshung
force-pushed
the
public/tagged-pointer-prototype
branch
from
b108ce2 to
199ee57
Compare
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 is a combination of two independent investigations
Tagged pointer prototype - I attempted to hack the CoreCLR so that I replace a normal function pointer by a tagged MethodDesc/InterpreterMethodInfo to allow a pure interpreted execution (i.e. no dynamic code generation). The prototype does not work completely, it only works for a few calls, but it shows how this could be done.
ReadyToRun interpreter integration study - this one is NOT implemented, this just resulted in a document describe how the current code work for a particular scenario (ReadyToRun code calls a static method) and where in the code we could change to implement something quickly for this particular case.
This is meant to be shared, not meant to be merged.