diff options
| author | Alon Zakai <alonzakai@gmail.com> | 2015-11-11 20:51:01 -0800 |
|---|---|---|
| committer | Alon Zakai <alonzakai@gmail.com> | 2015-11-11 20:51:01 -0800 |
| commit | 10c67d791dca5db1feb388db3afa21e8077d7ff5 (patch) | |
| tree | ed1ea371a9b95d6e70805a3122a069ad7b8b2e2f | |
| parent | 1ac690c7adddebeaa4d73a96bca0153b5f92db5b (diff) | |
| download | binaryen-10c67d791dca5db1feb388db3afa21e8077d7ff5.tar.gz binaryen-10c67d791dca5db1feb388db3afa21e8077d7ff5.tar.bz2 binaryen-10c67d791dca5db1feb388db3afa21e8077d7ff5.zip | |
faq movement
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -131,11 +131,11 @@ Same as Emscripten: MIT license. ## FAQ -### How does `asm2wasm` relate to the new WebAssembly backend which is being developed in upstream LLVM? +#### How does `asm2wasm` relate to the new WebAssembly backend which is being developed in upstream LLVM? This is separate from that. `asm2wasm` focuses on compiling asm.js to WebAssembly, as emitted by Emscripten's asm.js backend. This is useful because while in the long term Emscripten hopes to use the new WebAssembly backend, the `asm2wasm` route is a very quick and easy way to generate WebAssembly output. It will also be useful for benchmarking the new backend as it progresses. -### Why the weird name for the project? +#### Why the weird name for the project? **Binaryen** is a combination of **binary** - since WebAssembly is a *binary* format for the web - and **Emscripten** - which it can integrate with in order to compile C and C++ all the way to WebAssembly, via asm.js. Binaryen began as Emscripten's WebAssembly processing library (`wasm-emscripten`). |