Stream: git-wasmtime

Topic: wasmtime / issue #4255 Does wasmtime support interpreter ...

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:06):

Zhangyx24 opened issue #4255:

Does wasmtime support interpreter mode?

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:18):

cfallin commented on issue #4255:

Hi @Zhangyx24 -- unfortunately no, we do not currently have an interpreter backend for Wasm execution. This is something we would be open to having, if someone is interested in building it, but currently I'm not aware of anyone who is planning to do so.

I'll go ahead and close this issue since the question is answered but again, we're happy to talk further if someone wants to build this!

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:18):

cfallin closed issue #4255:

Does wasmtime support interpreter mode?

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:32):

Zhangyx24 commented on issue #4255:

Thanks for you answer!
Can I assume that wasmtime supports only JIT and AOT modes?

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:32):

Zhangyx24 deleted a comment on issue #4255:

Thanks for you answer!
Can I assume that wasmtime supports only JIT and AOT modes?

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:33):

Zhangyx24 commented on issue #4255:

@cfallin Thanks for your answer!
Can we assume that wasmtime supports only JIT and AOT modes?

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:37):

cfallin commented on issue #4255:

Yes, it supports both JIT and AOT. wasmtime run file.wasm will JIT by default, while wasmtime compile file.wasm will produce an AOT object file.cwasm, and you can then do wasmtime run --allow-precompiled file.cwasm.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:38):

cfallin commented on issue #4255:

(To clarify a bit more: the default "JIT" is an all-at-once compilation at load time, so it does not JIT on-demand as functions call each other, for example. But it is codegen in-process just before running the code, so in that sense it is a JIT.)

view this post on Zulip Wasmtime GitHub notifications bot (Jun 10 2022 at 03:40):

Zhangyx24 commented on issue #4255:

Thank you very much! I feel much clearer.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 22 2023 at 13:12):

hungryzzz commented on issue #4255:

(To clarify a bit more: the default "JIT" is an all-at-once compilation at load time, so it does not JIT on-demand as functions call each other, for example. But it is codegen in-process just before running the code, so in that sense it is a JIT.)

Hi, so even on the JIT mode, the code will be only compiled once, right? And it will not be optimized during execution?

view this post on Zulip Wasmtime GitHub notifications bot (Feb 22 2023 at 13:47):

bjorn3 commented on issue #4255:

Indeed. Wasmtime doesn't have multiple optimization tiers, nor speculative optimization. All compilation happens at once when creating the Module from a wasm module.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 22 2023 at 14:10):

hungryzzz commented on issue #4255:

Okay, I got it! Thank you for your answer!

Last updated: Dec 23 2024 at 13:07 UTC