Stream: git-wasmtime

Topic: wasmtime / issue #3328 wasmtime will support compile and ...

view this post on Zulip Wasmtime GitHub notifications bot (Sep 11 2021 at 07:58):

flyflypeng opened issue #3328:

I read the post Bytecode Alliance: One year update, which have announced that "The Lucet and Wasmtime teams join forces", so I have a question, wasmtime will port the benefits of the lucet runtime to support AOT style execution model?

view this post on Zulip Wasmtime GitHub notifications bot (Sep 11 2021 at 12:18):

tschneidereit commented on issue #3328:

This is indeed implemented now: you can use wasmtime compile your.wasm and then run it with wasmtime run your.cwasm, or load it in your embedding.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 11 2021 at 12:18):

tschneidereit commented on issue #3328:

I'll close this issue as I don't think there's anything else to address here, but feel free to open new issues if problems arise in using Wasmtime! :)

view this post on Zulip Wasmtime GitHub notifications bot (Sep 11 2021 at 12:18):

tschneidereit closed issue #3328:

I read the post Bytecode Alliance: One year update, which have announced that "The Lucet and Wasmtime teams join forces", so I have a question, wasmtime will port the benefits of the lucet runtime to support AOT style execution model?

view this post on Zulip Wasmtime GitHub notifications bot (Sep 13 2021 at 17:15):

peterhuene commented on issue #3328:

Please note: currently running a AOT compiled module using wasmtime run is not supported (this changed back in April) as it is considered an unsafe operation to deserialize a pre-compiled module (see comment here).

Right now you will need to write your own version of wasmtime run that uses Module::deserialize (or better yet the recently added Module::deserialize_file) to load the module.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 13 2021 at 17:15):

peterhuene edited a comment on issue #3328:

Please note: currently running an AOT compiled module using wasmtime run is not supported (this changed back in April) as it is considered an unsafe operation to deserialize a pre-compiled module (see comment here).

Right now you will need to write your own version of wasmtime run that uses Module::deserialize (or better yet the recently added Module::deserialize_file) to load the module.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 13 2021 at 17:20):

peterhuene commented on issue #3328:

Actually, it looks like @alexcrichton already put up a PR to restore this functionality to wasmtime run (that's what I get for going from oldest to newest in my github notifications :upside_down:).

Last updated: Dec 23 2024 at 13:07 UTC