bjorn3

> No println! There is no reason why a compiler backend or wasmparser should ever want to print to stdout. If they ever start doing this I would immediately open...

> Okay. From a beginner's perspective, the document on no_std support claims that the JIT compiler won't work as well due to its dependency on "mmap for allocating JIT code...

> build-std ought to get most uses most of the way, are you unable to use a nightly Cargo? `-Zbuild-std` only gives a non-feature-gated libstd on already existing targets. If...

There are two kinds of wasi programs: * commands: These are like executables and need `_start` invoked one time. Once it returns you are no longer allowed to call into...

WASI's `_start` and the wasm start function are entirely separate. The wasm start function is always called during module instantiation, before you get access to the wasm module instance. Because...

Cranelift could get no_std support, but wasmtime can't as it depends on the OS for example for mapping memory with the right priveleges.

> For platforms that don't have std, use a trait for host operations and require the program to implement functionality for mmap themselves, as I explained above. Same for anything...

To quote @cfallin from https://github.com/bytecodealliance/wasmtime/issues/4669#issuecomment-1210997950 (which is another debuginfo issue): > We currently don't have anyone on the project who understands our DWARF-handling code well and has time to work...

I don't think we preserve custom sections in precompiled modules.

> Is it actually our business to demangle symbols to begin with? 🤔 For the `Display` impls, IMO yes as `Display` is meant for human consumption and mangled symbol names...