Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Support using JSPI to load the secondary wasm split module. (#5431) | Brendan Dahl | 2023-01-20 | 1 | -0/+10 |
| | | | | | | | | | | When using JSPI with wasm-split, any calls to secondary module functions will now first check a global to see if the module is loaded. If not loaded it will call a JSPI'ed function that will handle loading module. The setup is split into the JSPI pass and wasm-split tool since the JSPI pass is first run by emscripten and we need to JSPI'ify the load secondary module function. wasm-split then injects all the checks and calls to the load function. | ||||
* | [Wasm GC] Do not refine types of exported globals in closed world (#5380) | Alon Zakai | 2023-01-03 | 1 | -9/+2 |
| | | | | | | Doing so can cause us to switch from a private type to a public type and error. Also refactor export-utils to make this easy. | ||||
* | [NominalFuzzing] SignatureRefining: Ignore exported functions (#4601) | Alon Zakai | 2022-04-22 | 1 | -0/+36 |
This hits the fuzzer when it tries to call reference exports with a null. |