Yerzhan Zhamashev

I can try working on this in the next couple of weeks since I already worked with code around host update/scale and wash #1978. I am motivated to understand the...

@thomastaylor312 yes, let's do it

I can add a fix in `wash-cli` if there are no expected changes to the documentation instead. I will wait for confirmation

Seems to align with the goal of "preventing a user from unintentionally running two different versions on two different hosts" described in #1818.

I applied changes to `libunwind` from https://gist.github.com/yamt/b699eb2604d2598810a2876ff2ffc8d8 and added `libunwind` to be included in wasi-sdk sysroot build. I made sure to use `-fwasm-exceptions` and `-mllvm -wasm-use-legacy-eh=false` where possible, but I...

Ok, my attempts to fix the older version of llvm project were irrelevant, sorry. As a note for people like me who used the latest release of wasi-sdk (28) and...

I tested wasi-sdk build result with the newest version wasmtime and it worked, yes. I was super happy to see C++ with exceptions working without requiring me to rewrite a...

If this helps anyone locally experimenting with exceptions-enabled builds of wasi-sdk sysroot: https://gist.github.com/yerzham/302efcec6a2e82c1e8de4aed576ea29d. Works after https://github.com/llvm/llvm-project/pull/168449 lands here. Tested with different C++ exception scenarios using wasmtime 38, basically has [same...

> (c) perhaps there are Emscripten patches to libunwind which haven't made their way into LLVM itself. I see libunwind in emscripten is built only with `Unwind-wasm.c` and `libunwind/include` header...