3 ms·
What major implementations are using LLVM? Firefox is using Cranelift, Chrome is using V8, both of these shouldn't be using LLVM, AFAIK, or am I wrong?
by TomMarius 7y ago
What major implementations are using LLVM? Firefox is using Cranelift, Chrome is using V8, both of these shouldn't be using LLVM, AFAIK, or am I wrong?
- rapsey 7y agoLLVM more usable for cloud vendors and such who use wasm outside of the browser. So we do have 3 quality implementations already.
- xuejie 7y agowasmer [1] has a LLVM backend, WAVM [2] uses LLVM as the bakend, I could be wrong but last time I checked, cranelift is only meant to be the next generation WASM engine used in Firefox, it is not yet in production. And actually the argument is: all of v8, Firefox/Cranelift and LLVM used in wasmer requires non-trivial work to make WASM fast, which shouldn't be needed given a different model. [1] https://github.com/wasmerio/wasmer/tree/master/lib/llvm-backend https://github.com/wasmerio/wasmer/tree/master/lib/llvm-back... [2] https://github.com/WAVM/WAVM https://github.com/WAVM/WAVM
- DagAgren 7y agoI highly doubt that there is another model that would not require non-trivial work to be fast, while also being reasonably portable to different architectures. Sure, we could be faster by just sending x86 machine code, but that isn't really the point.