mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2024-10-16 13:02:32 +00:00
562a5dd1b6
Currently, `data.drop` instruction is implemented by directly modifying the underlying module. It breaks use cases where you have multiple instances sharing a single loaded module. `elem.drop` has the same problem too. This PR fixes the issue by keeping track of which data/elem segments have been dropped by using bitmaps for each module instances separately, and add a sample to demonstrate the issue and make the CI run it. Also add a missing check of dropped elements to the fast-jit `table.init`. Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2735 Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2772 |
||
|---|---|---|
| .. | ||
| cg | ||
| fe | ||
| asmjit_sgx_patch.diff | ||
| iwasm_fast_jit.cmake | ||
| jit_codecache.c | ||
| jit_codecache.h | ||
| jit_codegen.c | ||
| jit_codegen.h | ||
| jit_compiler.c | ||
| jit_compiler.h | ||
| jit_dump.c | ||
| jit_dump.h | ||
| jit_frontend.c | ||
| jit_frontend.h | ||
| jit_ir.c | ||
| jit_ir.def | ||
| jit_ir.h | ||
| jit_regalloc.c | ||
| jit_utils.h | ||