This repository has been archived by the owner on Oct 3, 2023. It is now read-only.
chore(deps): update dependency paritytech/wasmi to v0.30.0 #6453
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 contains the following updates:
0.29.0
->0.30.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
paritytech/wasmi
v0.30.0
Compare Source
Changed
wasmi
bytecode memory consumption. (https://github.com/paritytech/wasmi/pull/718)wasmi
bytecode by organizing the instructionsinto so-called instruction words, effectively reducing the amount of bytes required per
wasmi
instruction 16 bytes to 8 bytes.There was an experiment with 4 bytes but experiments confirmed that 8 bytes per instruction
word was the sweetspot for
wasmi
execution and translation performance.for translation from Wasm to
wasmi
bytecode by roughly 15-20%.call
andreturn_call
for Wasm module internal calls. (https://github.com/paritytech/wasmi/pull/724)wasmi
bytecode now differentiates between calls to Wasm module internal functionsand imported functions which allows the
wasmi
bytecode executor to perform the commoninternal calls more efficiently.
call intense workloads of up to 30% in some test cases.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.