Chris Woods

We hope to have an initial contribution to WAMR with exception support in the next few months. There is such a swathe of C++ software in-particular that is excluded from...

Whooha... Rockstar's both of you, and I've got some reading to do. Thanks for the pointers. Let me take a look.

The `-fwasm-exceptions` flag allows the compiler to output the try / catch and other exception handling instructions in WebAssembly bytecode. But it is up to the language implementation to determine...

I apologize for the radio silence. Yes, we've made considerable progress and will post a design document next week (I'll add to this issue). An initial contribution to the exception...

The approach as outlined originally (above) changed somewhat. Focusing on the unclear specifications we worked on trying to provide clarity. This resulted in a light weight, WAMR specific specification document,...

Since this issue has been created, a new approach to exception handling was adopted by the CG - [Extern Ref B-Prime ](https://github.com/webassembly/exception-handling/tree/exnref-1b). This requires some additional reworking of the runtime...

> I've been trying to get exception support into my forks of LLVM 17, WASI SDK & WAMR, pretty much everything should be in place (including libunwind enablement) and Clang...

> is anyone here working on a new version of the proposal with exnref? We've done some initial comparison work, and it looks like the exnref version would be able...

> > > I've been trying to get exception support into my forks of LLVM 17, WASI SDK & WAMR, pretty much everything should be in place (including libunwind enablement)...

> One thing I don't quite understand is how these new features/extensions are meant to be delivered in a scenario where the runtime cannot be updated. Is it that the...