Sam Clegg

@dschuff said he to would take care of the node update. in the meantime disabling the test seems fine.

@bvibber I curious what LE platforms you are interested in targeting?

Given that we now have `SUPPORT_BIG_ENDIAN=1` maybe we can close this issue and open a new one to discuses the possibility of making the default?

Are you looking to run your emscripten modules on s390/Linux? Do chrome or firefox even run there?

> Also I have no particular investment in s390 nor any software I require running there, I simply wish the tooling I work with to be correct whereever it's run....

Won't this means that the version reported in the wasi-libc that is embedded in wasi-sdk is always at least one version behind because the building happens before the tagging? Or...

> i wonder if the git requirement can make some people unhappy. ie. you can't build from release tarballs like https://github.com/WebAssembly/wasi-libc/archive/refs/tags/wasi-sdk-22.tar.gz anymore. i don't have a nice solution though. Normally...

To be clear this is not some kind of regression? i.e. you are not claiming that some previous version of emscripten had a faster version of `MAIN_THREAD_EM_ASM`? As far as...

Are you doing anything on the main UI thread that is likely to be blocking it? i.e. are you doing synchronous proxying to your background thread? i.e. can you give...

So you have the following JS contexts: 0: The main browser UI thread 1: The worker that starts your wasm program 2. The worker that runs the `main` function inside...