Alon Zakai

> (Also we need to fix the new parser to handle this too, because currently it rejects parsing if a pop is nested) Good catch, the fuzzer found that bug...

I see now, sorry for misunderstanding before. Looks like that #4237 is from 2021, and we only added the guarantee of removing such blocks in 2022: the work was in...

@tlively I could use some advice on how to fix the parser here. This PR requires it to accept code like this: https://github.com/WebAssembly/binaryen/pull/6950/files#diff-9d8e4085cec9051d98d5f9c2d98eb679d3f5ada3a6fb8800725023595524cb1cR10 In the last commit I believe I...

Perhaps another option instead of this PR is, since this is in *old* EH, we can ignore the "pop must be in a catch" parser error in the fuzzer..?

@tlively Oh, I was thinking we didn't want to land this? Are you saying it would help the IRBuilder work? For that code sample, running the EH fixups helper should...

> Yes, but we probably don't want to do that every time we parse a module, right? Yeah, it's the same issue as with passes. We prefer not to run...

Yes, it is a little odd that typed arrays use the system endianness, while wasm Memories are always little endian. This is an issue for all emscripten output, because it...

@miladfarca Correct. Any time there is any JS - and there is by default, as wasm can't access Web APIs itself - then this is an issue. The only solutions...

> In terms of adding support using DataView, is this something we could contribute or emscripten would be able to add the changes and we can test it on BE...

Btw, there is a PR up to write `SAFE_HEAP` using acorn. That replaces `HEAP8` etc. usage with a call to a `SAFE_HEAP` function. An endianness fixup could do something similar...