diff options
| author | JF Bastien <jfb@chromium.org> | 2016-02-04 05:18:07 -0800 |
|---|---|---|
| committer | JF Bastien <jfb@chromium.org> | 2016-02-05 00:51:24 -0800 |
| commit | 3fbae879fc1b678e748ab3f8c24148e1c3818f45 (patch) | |
| tree | a0592797c47de742624a4d1e2011a459b2273a17 /src/asm_v_wasm.h | |
| parent | c1f9026c2788e4ef6f6af0c6d9aa04d22fc00320 (diff) | |
| download | binaryen-3fbae879fc1b678e748ab3f8c24148e1c3818f45.tar.gz binaryen-3fbae879fc1b678e748ab3f8c24148e1c3818f45.tar.bz2 binaryen-3fbae879fc1b678e748ab3f8c24148e1c3818f45.zip | |
Support start
As spec'd in: https://github.com/WebAssembly/design/pull/495
And discussed in: https://github.com/WebAssembly/spec/issues/231
This will make it simpler and more uniform to add a start entry point.
s2wasm is the right place to add start because it'll eventually need to
do other basic setup, e.g. put code in start to setup the stack, as
dschuff is doing in:
https://github.com/WebAssembly/binaryen/pull/179
Or rather, the linker is the right place and s2wasm happens to act as
our linker right now.
Diffstat (limited to 'src/asm_v_wasm.h')
0 files changed, 0 insertions, 0 deletions