Make tracer no_std compatible
#680
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
This requires a slight change to the API that is exposed to `jolt-core`: The `trace` function no longer takes a `PathBuf` (since that's not available in a `no_std` environment) and instead takes the elf contents as a `Vec<u8>`. This requires a slight change to the `jolt-core` `host` module to make that API change compatible.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 requires a slight change to the API that is exposed to
jolt-core: Thetracefunction no longer takes aPathBuf(since that's not available in ano_stdenvironment) and instead takes the elf contents as aVec<u8>. This requires a slight change to thejolt-corehostmodule to make that API change compatible.