3 ms·
I wonder how easy it would be to use JSC's WebAssembly backend separately from the rest of Webkit, and maybe even have it output to a static binary. And maybe c
by trishume 9y ago
I wonder how easy it would be to use JSC's WebAssembly backend separately from the rest of Webkit, and maybe even have it output to a static binary. And maybe connect its FFI with a different language than Javascript (maybe Go?).
Given the work that has gone into B3 it might make a good target IR for compilers that want fast compilation to native executables, and you'd get to target the web for free as a bonus.
- jfbastien 9y agoNot too bad. Some things are connected to GC and JIT-code generation, but if you wanted just BBQ or OMG (no tiering) something could be done. Tiering too, but then you have more of JSC in there, really depends what you want. Depending on what you want to do, there are a few experimental .wasm -> LLVM IR -> machine code things around. Problem is really what your embedder would be. Import / export is what you'd have to define! In JavaScript we have a standardized API for that.