mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2025-02-06 23:15:16 +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 |
||
|---|---|---|
| .. | ||
| build_docker_images.yml | ||
| build_iwasm_release.yml | ||
| build_llvm_libraries.yml | ||
| build_wamr_lldb.yml | ||
| build_wamr_sdk.yml | ||
| build_wamr_vscode_ext.yml | ||
| build_wamrc.yml | ||
| coding_guidelines.yml | ||
| compilation_on_android_ubuntu.yml | ||
| compilation_on_macos.yml | ||
| compilation_on_nuttx.yml | ||
| compilation_on_sgx.yml | ||
| compilation_on_windows.yml | ||
| create_tag.yml | ||
| hadolint_dockerfiles.yml | ||
| nightly_run.yml | ||
| release_process.yml | ||
| reuse_latest_release_binaries.yml | ||
| spec_test_on_nuttx.yml | ||