Wasmtime GitHub notifications bot (Dec 18 2023 at 11:11): Wasmtime GitHub notifications bot (Dec 18 2023 at 11:11):LordCasser opened issue #7700:
There is just a use case, I'd like to make the wasm JIT compiler a part of VM-OS.
Wasmtime GitHub notifications bot (Dec 18 2023 at 16:16):alexcrichton commented on issue #7700:
You'll find some more discussion about this here, but I'll also want to point out this section of our documentation. If you have a target you're interested in supporting we'd love to discuss more, but
#![no_std]won't work "out of the box" today.In terms of bare-bones requirements Wasmtime at this time requires virtual memory (e.g. an MMU). I've got a branch I haven't upstreamed which distills Wasmtime's base runtime requirements to this C API which would need to be supported by the system.
Wasmtime GitHub notifications bot (May 10 2024 at 02:13):alexcrichton closed issue #7700:
There is just a use case, I'd like to make the wasm JIT compiler a part of VM-OS.
Wasmtime GitHub notifications bot (May 10 2024 at 02:13):alexcrichton commented on issue #7700:
Wasmtime now supports no_std itself and otherwise having Cranelift support it is tracked at https://github.com/bytecodealliance/wasmtime/issues/1158, so I'm going to close this.
Last updated: Dec 23 2024 at 12:05 UTC