[RISC-V] Port Mono for RISC-V 64 Arch (2/3) thunk & tramponlie #83715
Conversation
This file contains 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
ghost
added
the
community-contribution
This was referenced Mar 21, 2023
Xinlong-Wu
force-pushed
the
ready-to-pr-2
branch
from
3f65b7a
to
ea5ebad
Compare
vargaz
approved these changes
Apr 3, 2023
|
There are conflicts between the 3 PRs, so only the first could be merged. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
These patches initially ported the JIT of MonoVM to
RISC-V 64 imafdcArch, withinglp64dABI.So that the runtime can run and output
hello worldto command line by MonoVM under these patchesThis patch generates some of the thunk and tramponline used by the RISC-V64 architecture in MonoVM, allowing JIT code to be called between each other. There is also some exception-related code implemented in this process, but the current milestone only successfully outputs "Hello World", so some of the exception-related code may not have been tested.
ps. Only applying this patch may not compile successfully, splitting the patch is only for review purposes. more info please refer to #36748