[llvm] WebAssembly: Stop changing MCAsmInfo's ExceptionsType based on flags (PR #146343)

[Heejin Ahn via llvm-commits]

aheejin wrote:

> > @mcbarton For me `-fwasm-exception -mllvm -wasm-enable-sjlj` works fine. Also this PR is not supposed to change the behavior wrt clang arguments. If you continue to experience issues, please file a separate bug with a reproducer.
> 
> Unfortunately this does not work for us and the error message does not seem to be telling anything. We are executing clang-based wasm code in memory. Coming up with a reproducer will be particularly challenging.

I'm not sure what "executing clang-based wasm code in memory" means, but if a specific combination of flags doesn't work, it usually doesn't work for all files, no? Even if the error message doesn't seem to tell much, I think pasting it is helpful than not pasting it.

> > In general users should really not be using -mllvm flags; they're mostly intended as backend debugging options. If users need one of these, they should be routing through a stable clang driver flag.
> 
> Agreed. However, right now our downstream client is broken without a reasonable path forward. I am not sure how to debug this. What is the high-level clang flag that produces these effects in the backend which we can use?

I'm not sure what "these effects" are. I don't have any info on what your bug looks like at this point. Please file a separate issue with some more info.

https://github.com/llvm/llvm-project/pull/146343