-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge changes from AntelopeIO #9
Merged
Merged
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
Collaborator
swatanabe
commented
Sep 13, 2023
•
edited
Loading
edited
- store wasm globals in execution context such that a single parsed module can be shared by multiple threads AntelopeIO/eos-vm#16
- Parse WASM code only once for JIT AntelopeIO/eos-vm#18
- Use a single execution context per wasm interface (per thread) instead of per contract AntelopeIO/eos-vm#19
- support for single wasm interface AntelopeIO/eos-vm#20
- Move mutable data in elem and data segments into execution context to match the new storage of globals
- Simplify module layout
Change eosnetworkfoundation/mandel-eos-vm to AntelopeIO/eos-vm in eos-vm submodule
Remove EOSIO references; delete CONTRIBUTING.md and IMPORTANT.md
fix is_callable_v
…,uint32_t)`) results in a "statement has no effect [-Werror=unused-value]" warning. Dissable `unused-value` for this function.
Remove -Wall warnings
In C++20, a struct with a declared constructor is not an aggregate anymore, so attempts to construct these with initializer_lists throughout the code fail.
Remove unneeded declared constructor.
[3.x] EOS VM memory issues fix
[3.x -> 4.0] EOS-VM: merge memory issue fix from release/3.x
…ssue_fix_from_4_0
[4.0 -> main] EOS-VM: merge memory issue fix from release/4.0
…ule can be shared by multiple threads
store wasm globals in execution context such that a single parsed module can be shared by multiple threads
Parse WASM code only once for JIT
Use a single execution context per wasm interface (per thread) instead of per contract
…module is changed.
support for single wasm interface
Further reading on what these eos-vm changes enable can be found here. |
James-Mart
approved these changes
Sep 14, 2023
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.