asmble

Depends on what you mean by hoops (ala clang), but there is Graal which can run LLVM bitcode [0] but I am unsure if it can compile it. I have personally compiled C code to WASM and then to the JVM via [1]. C/C++ are complex (and/or have complex optimizations) so a compiler should be used, but doesn't necessarily have to target a specific CPU but still have to have a bit-preference and what not. And of course once you interact with the system, some abstraction has to occur somewhere. 0 - http://www.graalvm.org/docs/getting-started/#running-llvm-in... 1 - https://github.com/cretz/asmble

That line is labelled with https://github.com/cretz/asmble

> incorrectly labeled as targeting Java Bytecode https://github.com/cretz/asmble The name of that tool is even labelled in the graph!

Quite directly[0] :-) There's even an example using Rust regex on the JVM to get speedups in some cases [1]. 0 - https://github.com/cretz/asmble 1 - https://github.com/cretz/asmble/tree/master/examples/rust-re...

> I'm so excited about WebAssembly, but really not because of the web. You and me both. I wrote a backend for the JVM [0] and there is one in dev targetting native [1] (in Rust using an interesting alt-llvm project [2]). I suspect where you'll start to see this really shine is when a popular langauge targets WASM as the primary target and lets second-level backends compile to a specific arch. The other problem is interoperability. Until host bindings come along and the community standardizes on things like string representation and syscalls, many of uses are siloed by the frontend compilers. I think we can do better than libc+posix. 0 - https://github.com/cretz/asmble 1 - https://github.com/sunfishcode/wasmstandalone 2 - https://github.com/Cretonne/cretonne

See http://webassembly.org/docs/non-web/. Portability. For example, I can use Rust on the JVM: https://github.com/cretz/asmble/tree/master/examples/rust-re...

Yup: https://github.com/cretz/asmble

Not only in JS, I got decent performance with Rust's regex engine compiled to WASM then compiled to the JVM: https://github.com/cretz/asmble/tree/master/examples/rust-re.... And that's without any extreme optimization on the JVM side.

Yup, I use those unsigned methods, e.g. https://github.com/cretz/asmble/blob/3cb439e887245f23bf876e8.... Luckily WASM only has 32/64 bit integer arithmetic.

There seems to be a good deal of info in the README: https://github.com/cretz/asmble#compilation-details I haven't dug deeply but it seems from the documentation that the project is trying to do things the 'right' way (mapping instructions to JVM bytecodes at a low level)... as opposed to, say, trying somehow to compile to Java code.

For the reverse, I wrote a WASM-to-JVM compiler: https://github.com/cretz/asmble. I think WASM has the ability for us to finally cross the language boundaries without marrying ourselves to C/C++ ABI. But at this early stage, there's no common stdlib for all languages to share.