Making WebAssembly better for Rust and for all languages

Re:Making WebAssembly better for Rust and for all languages by singularity2001 on Wednesday March 14, 2018 @01:36PM (#16586623)

node(v8) and all browsers compile Wasm->native ad hoc

[ Parent | on HN ]

Re:Making WebAssembly better for Rust and for all languages by pionar on Wednesday March 14, 2018 @03:51PM (#16587721)

I believe the grandparent was talking about machine-language. Take some WASM, produce an EXE, for example.

[ Parent | on HN ]

Re:Making WebAssembly better for Rust and for all languages by KMag on Thursday March 15, 2018 @01:15AM (#16590559)

In this context, "native" and "machine-language" are synonymous, and V8/Node do in fact generate native code/machine-language from WASM. The GP did correctly answer the OP's question, but it's not clear if the OP had a more specific question in mind.

The phrase you're looking for is "Ahead-of-Time" or "AoT" compiler. It's not clear if the OP was specifically looking for an AoT compiler, or if a JIT suffices for her/his use case.

[ Parent | on HN ]

Re:Making WebAssembly better for Rust and for all languages by imtringued on Thursday March 15, 2018 @08:44AM (#16592310)

I don't really think there is any demand for that. The generated WASM code is already optimized. The JIT is basically a very fast AOT compiler. The only advantage you're gaining is faster startup time and that could perhaps be achieved by caching the generated machine code on disk.

[ Parent | on HN ]

Re:Making WebAssembly better for Rust and for all languages by CryZe on Thursday March 15, 2018 @04:06PM (#16596126)

I compiled a GB emulator written in WASM to Rust yesterday and benchmarked it. The Rust one was about 7 times faster.

[ Parent | on HN ]