mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2025-05-17 15:11:13 +00:00
![]() 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 |
||
---|---|---|
.. | ||
jit_emit_compare.c | ||
jit_emit_compare.h | ||
jit_emit_const.c | ||
jit_emit_const.h | ||
jit_emit_control.c | ||
jit_emit_control.h | ||
jit_emit_conversion.c | ||
jit_emit_conversion.h | ||
jit_emit_exception.c | ||
jit_emit_exception.h | ||
jit_emit_function.c | ||
jit_emit_function.h | ||
jit_emit_memory.c | ||
jit_emit_memory.h | ||
jit_emit_numberic.c | ||
jit_emit_numberic.h | ||
jit_emit_parametric.c | ||
jit_emit_parametric.h | ||
jit_emit_table.c | ||
jit_emit_table.h | ||
jit_emit_variable.c | ||
jit_emit_variable.h |