wasm-micro-runtime/core/iwasm
YAMAMOTO Takashi 562a5dd1b6
Fix data/elem drop (#2747)
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
2023-11-18 08:50:16 +08:00
..
aot Fix data/elem drop (#2747) 2023-11-18 08:50:16 +08:00
common Fix printing ref.extern addresses in wasm_application.c (#2774) 2023-11-16 15:10:58 +08:00
compilation Fix data/elem drop (#2747) 2023-11-18 08:50:16 +08:00
doc Add architecture diagram for wasm globals and classic-interp stack frame (#2058) 2023-03-25 09:39:20 +08:00
fast-jit Fix data/elem drop (#2747) 2023-11-18 08:50:16 +08:00
include Merge branch main into dev/wasi-libc-windows 2023-11-09 10:13:59 +08:00
interpreter Fix data/elem drop (#2747) 2023-11-18 08:50:16 +08:00
libraries Use next generation crypto API on Windows (#2769) 2023-11-17 18:40:29 +08:00
README.md Add architecture diagram for wasm globals and classic-interp stack frame (#2058) 2023-03-25 09:39:20 +08:00