Heejin Ahn

@sbc100 > True, once multi-value is universally available we could just assume it when we build compiler-rt. > > In emscripten we will want to continue to support targets without...

> > @alexcrichton > > > If I might throw out another possible alternative, could it perhaps also be possible to write this down in source itself? > > >...

I am not familiar with how Rust exceptions are compiled; more precisely, how Rust is using our JS libraries written for C++. Can you provide an .ll file and a...

Sorry for the late reply. Yeah your bitcode files contain a bunch of `invoke`s, but these shouldn't be converted to `invoke_vi` -like calls unless you run [WebAssemblyLowerEmscriptenEHSjLj](https://github.com/llvm/llvm-project/blob/main/llvm/lib/Target/WebAssembly/WebAssemblyLowerEmscriptenEHSjLj.cpp). For clang, this...

This happens because Rust programs that use LLVM Itanium EH IR may not use `__cxa_end_catch`, but still need `setThrew` because of `invoke`s. A similar thing happened for Emscritpen SjLj so...

Thanks! Where am I supposed to add `setThrew`, `EXPORTED_FUNCTIONS` or `DEFAULT_LIBRARY_FUNCS_TO_INCLUDE`? I have been always confused about the uses of those two...

In emcc + C++, if you set `DISABLE_EXCEPTION_CATCHING`, that `LowerEmscriptenEHSjLj` pass would not run and references to `invoke`s or `setThrew` are not gonna be generated. But I guess you use...

If you don't use `emcc`, which tool did you feed `-sEXPORTED_FUNCIONS=_setThrew` to?

I think this makes sense. I don't think we've considered something like this. (Also we need to fix the new parser to handle this too, because currently it rejects parsing...

#4237 seems to say the binary was rejected at compile time from the engine. Does that mean we didn't omit the unnamed blocks in binary then? If we did why...