Stream: git-wasmtime

Topic: wasmtime / Issue #1603 Cannot virtualize WASI imports today

Wasmtime GitHub notifications bot (Apr 27 2020 at 14:42):

alexcrichton opened Issue #1603:

This is an issue specific for this repository spawned from https://github.com/bytecodealliance/wasmtime-py/issues/2. Unfortunately it is not possible to virtualize WASI imports and functionality today where the virtualization may eventually delegate to the original implementations. The reason for this has to do with how the original module's linear memory makes its way to the wasi instance. Today this is done via the Caller structure, but this is brittle because once virtualized your Caller is different.

AFAIK we don't have a great answer for this today until we can figure out how to create a WASI instance with a memory or something like that.

Wasmtime GitHub notifications bot (Apr 27 2020 at 14:42):

alexcrichton labeled Issue #1603:

This is an issue specific for this repository spawned from https://github.com/bytecodealliance/wasmtime-py/issues/2. Unfortunately it is not possible to virtualize WASI imports and functionality today where the virtualization may eventually delegate to the original implementations. The reason for this has to do with how the original module's linear memory makes its way to the wasi instance. Today this is done via the Caller structure, but this is brittle because once virtualized your Caller is different.

AFAIK we don't have a great answer for this today until we can figure out how to create a WASI instance with a memory or something like that.

Wasmtime GitHub notifications bot (Apr 27 2020 at 14:42):

alexcrichton labeled Issue #1603:

This is an issue specific for this repository spawned from https://github.com/bytecodealliance/wasmtime-py/issues/2. Unfortunately it is not possible to virtualize WASI imports and functionality today where the virtualization may eventually delegate to the original implementations. The reason for this has to do with how the original module's linear memory makes its way to the wasi instance. Today this is done via the Caller structure, but this is brittle because once virtualized your Caller is different.

AFAIK we don't have a great answer for this today until we can figure out how to create a WASI instance with a memory or something like that.

Last updated: Nov 22 2024 at 16:03 UTC