Sorry if I've asked you this already, but what is you use case for bigendian suport @slavek-kucera ? Are you running in production on actual BE machines?

Yes, the output targets s390x running z/os.

As for testing, I guess we could add bigendian3 test suite (assuming @juj still runs it in the private pipeline).

As for testing, I guess we could add bigendian3 test suite (assuming @juj still runs it in the private pipeline).

I totally do. (e.g. http://clbri.com:8010/#/builders/11/builds/1275 - ignore lots of red for other failures, but there's a passing bigendian0 at the very bottom of the page)

Posted PR #25820 to complete the testing matrix. After that lands, I can add the remaining bigendian suites onto the test runner list.

Yes, the output targets s390x running z/os.

What engine are you running the emscripten output on? i.e. Are these servers running Nodejs I guess?

Yes, the engine is nodejs.

@slavek-kucera My Linux box now completed run of all the bigendian suites. It looks like there are some failures in -O2 and -Os modes: http://clbri.com:8010/#/builders/11/builds/1278

I think those are all false positive build failures due to closure compiler.

Function LE_ATOMICS_WAITASYNC: called with 3 argument(s). Function requires at least 4 argument(s) and no more than 4 argument(s)

Maybe the function needs an annotation just like Atomics.waitAsync?