Subzero. WASM. Additional progress.

c2wasm-exe.sh

Index: c2wasm-exe.sh
diff --git a/c2wasm-exe.sh b/c2wasm-exe.sh
new file mode 100755
index 0000000000000000000000000000000000000000..4c73ac6511b69cc810b9425c5be4be8fc6469b2f
--- /dev/null
+++ b/c2wasm-exe.sh
@@ -0,0 +1,10 @@
+#!/bin/bash
+
+# TODO (eholk): This script is a hack for debugging and development
+# that should be removed.
+
+./wasm-install/bin/emscripten/emcc "$1" -s BINARYEN=1 \

[Derek Schuff, 2016/04/15 16:13:23]

This invocation of emcc will use whatever configuration you happen to have in
your ~/.emscripten file, and may not match what the waterfall uses. To try to
make things more hermetic, the waterfall has 2 config files: emscripten_config
(which uses the fastcomp/asm.js backend, which will use asm2wasm if you use
BINARYEN=1) and emscripten_config_vanilla (which uses the wasm backend
directly). There are 2 different config files because they have different
LLVM_ROOT paths to different builds of LLVM. You can specify the emscripten
config file with the --em-config flag.

[Eric Holk, 2016/04/15 16:16:59]

Thanks for the suggestion. I'll include the --em-config option in my next CL.

+  -s 'BINARYEN_METHOD="native-wasm"' -O2 && \
+./wasm-install/bin/sexpr-wasm a.out.wast -o a.out.wasm && \
+./pnacl-sz a.out.wasm -o a.out.o -filetype=obj -O2 && \
+clang -m32 a.out.o runtime/wasm-runtime.c -g