So now my current emscripten-new branch seems to cleanly run the tests for asmjs-unknown-emscripten. The libc wasm32 patches are upstream. My next steps are to get the fastcomp patches merged, rebase brson/emscripten-new onto rust-lang/master, and post a PR to Rust.
In the meantime @rschulman is looking to get compiletest working with wasm32-unknown-emscripten. There’s a PR against emscripten to add some missing math intrinsics.
Additional work for people to pick up include:
- Going through all the many failing asmjs-unknown-emscripten tests and seeing if any can be fixed. A lot of them seem like they relate to various options that may be configurable in emscripten (like resizable heaps, networking and filesystem support), and it’s not clear how or whether we should deal with them in-tree (I suspect they can be dealt-with as
-C link-argsand std doesn’t need to care, but maybe the test runner should be tweaked to change the emcc configuration. not sure; needs investigation). - Fixing unwinding. This is a deep problem and requires fixes in Rust and emscripten. Needs a hero.
- Start coming up with mindblowing demos and libraries. An idea I had this morning was a project to collect a few production-ready javascript libraries written in Rust that web programmers can just download and use without dealing with the Rust side. Present it in a nice website that looks appealing to web devs like a real product.