I came across a clang bug and it seemed that it has been already fixed 
upstream but since emscripten uses the fastcomp fork which is isn't that up 
to day I got a thought about WebAssembly.
Since LLVM has a WebAssembly back-end and the binaryen toolchain contains a 
WebAssembly to asm.js converter, isn't it possible to completely drop the 
fastcomp fork in favor of LLVM's WebAssembly back-end + wasm2asm?
This would have advantages like using "vanilla" LLVM (Which reduces 
complexity in the emscripten toolchain as there is no need to keep the fork 
updated) + latest upstream fixes + latest optimizations.

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to