Move execution context into a seperate crate#598
Merged
mssun merged 1 commit intoapache:masterfrom Jan 8, 2022
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.
Description
Teaclave execution crate exports several APIs such as
reset_thread_context,reset_thread_context, andc_open_input. These APIs are used by statically linked non-rust executors likemesapyandwamrto read/write files from the execution service.However, the above APIs are not accessible to the built-in functions because build-in functions are in a different crate
teaclave_function.teaclave_functionis the dependency of the crateteaclave execution.This PR moves these APIs into a separate crate so build-in functions can invoke these APIs directly.
How has this been tested?
CI test.
Checklist
master.