mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2025-10-31 13:17:31 +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 |
||
|---|---|---|
| .. | ||
| uncommon | ||
| bh_assert.c | ||
| bh_assert.h | ||
| bh_atomic.h | ||
| bh_bitmap.c | ||
| bh_bitmap.h | ||
| bh_common.c | ||
| bh_common.h | ||
| bh_hashmap.c | ||
| bh_hashmap.h | ||
| bh_list.c | ||
| bh_list.h | ||
| bh_log.c | ||
| bh_log.h | ||
| bh_platform.h | ||
| bh_queue.c | ||
| bh_queue.h | ||
| bh_vector.c | ||
| bh_vector.h | ||
| gnuc.h | ||
| runtime_timer.c | ||
| runtime_timer.h | ||
| SConscript | ||
| shared_utils.cmake | ||