-
Notifications
You must be signed in to change notification settings - Fork 2.6k
sc-executor-wasmtime: upgrade wasmtime to 0.30.0 #10003
Conversation
Changes related to memory64 proposal implementation, for additional details see bytecodealliance/wasmtime#3153
/// | ||
/// The default is `None`. | ||
pub max_memory_pages: Option<u32>, | ||
pub max_memory_size: Option<usize>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not continue to use pages here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be aligned with wasmtime interface and avoid intermediate layer of converting it to bytes.
The change in upstream also makes sense, the reasoning (link in the first commit):
The runtime implementation of mmap-based linear memories has changed
to largely work in usize quantities in its API and in bytes instead
of pages. This simplifies various aspects and reflects that
mmap-memories are always bound by usize since that's what the host
is using to address things, and additionally most calculations care
about bytes rather than pages except for the very edge where we're
going to/from wasm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay :)
bot merge |
Trying merge. |
Resolves #9605
Resolves #9606
polkadot companion: paritytech/polkadot#4063