Re:WebAssembly and Back Again: Fine-Grained Sandboxing in Fi...
by fyrn- on Monday December 06, 2021 @02:42PM
(#29464571)
Not back into C, from WASM to native executable / asm / object code
[ Parent
| on HN ]
Re:WebAssembly and Back Again: Fine-Grained Sandboxing in Fi...
by bholley on Monday December 06, 2021 @03:09PM
(#29464929)
Deukhoofd is correct — we compile the WASM code back into C in order to reuse and reduce friction with our existing compilation pipeline.
Re:WebAssembly and Back Again: Fine-Grained Sandboxing in Fi...
by wfh on Tuesday December 07, 2021 @10:43AM
(#29473644)
How does this compare with https://chromium-review.googlesource.com/c/chromium/src/+/27... ?
Re:WebAssembly and Back Again: Fine-Grained Sandboxing in Fi...
by flohofwoe on Monday December 06, 2021 @03:44PM
(#29465428)
The solution described in the post actually translates C/C++ to WASM, and then translates the WASM bytecode back to C (via a tool called wasm2c), which is then fed back into the C compiler again to compile to native code, all 'offline' in the Firefox build process.