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
6 lines
184 B
Markdown
6 lines
184 B
Markdown
The "shared-module" sample project
|
|
==================================
|
|
|
|
This sample demonstrates a bug described in:
|
|
https://github.com/bytecodealliance/wasm-micro-runtime/issues/2735.
|