Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [wasm] Scan machine stack based on `ec->machine.stack_{start,end}` | Yuta Saito | 2022-11-06 | 1 | -3/+2 |
| | | | | | | | | fiber machine stack is placed outside of C stack allocated by wasm-ld, so highest stack address recorded by `rb_wasm_record_stack_base` is invalid when running on non-main fiber. Therefore, we should scan `stack_{start,end}` which always point a valid stack range in any context. | ||||
* | [wasm] add asyncify based setjmp, fiber, register scan emulation | Yuta Saito | 2022-01-19 | 1 | -0/+26 |
configure.ac: setup build tools and register objects main.c: wrap main with rb_wasm_rt_start to handle asyncify unwinds tool/m4/ruby_wasm_tools.m4: setup default command based on WASI_SDK_PATH environment variable. checks wasm-opt which is used for asyncify. tool/wasm-clangw wasm/wasm-opt: a clang wrapper which replaces real wasm-opt with do-nothing wasm-opt to avoid misoptimization before asyncify. asyncify is performed at POSTLINK, but clang linker driver tries to run optimization by wasm-opt unconditionally. inlining pass at wasm level breaks asyncify's assumption, so should not optimize before POSTLIK. wasm/GNUmakefile.in: wasm specific rules to compile objects |