c2wasm-exe.sh - Issue 1876413002: Subzero. WASM. Additional progress.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: c2wasm-exe.sh

Issue 1876413002: Subzero. WASM. Additional progress. (Closed) Base URL: https://chromium.googlesource.com/native_client/pnacl-subzero.git@master

Patch Set: Merging with master Created 4 years, 8 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 #!/bin/bash

	2

	3 # TODO (eholk): This script is a hack for debugging and development

	4 # that should be removed.

	5

	6 ./wasm-install/bin/emscripten/emcc "$1" -s BINARYEN=1 \
	Derek Schuff 2016/04/15 16:13:23 This invocation of emcc will use whatever configur 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-c Show quoted text On 2016/04/15 16:13:23, Derek Schuff wrote: > 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. Thanks for the suggestion. I'll include the --em-config option in my next CL.
	7 -s 'BINARYEN_METHOD="native-wasm"' -O2 && \

	8 ./wasm-install/bin/sexpr-wasm a.out.wast -o a.out.wasm && \

	9 ./pnacl-sz a.out.wasm -o a.out.o -filetype=obj -O2 && \

	10 clang -m32 a.out.o runtime/wasm-runtime.c -g

OLD	NEW

« no previous file with comments | « README-wasm.md ('k') | fetch-torture-tests.sh » ('j') | fetch-torture-tests.sh » ('J')