-
Notifications
You must be signed in to change notification settings - Fork 575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wasm shared heap #3544
Comments
If wasm shared heap is enable, should the boundary check keep enabled ? In the following code, if bounds checks is disabled, should we return the offset directly or judge whether the addr is in shared heap?
|
Would u mind giving us, the community, a quick introduction about:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implementation tasks:
add WAMR_BUILD_SHARED_HEAP and WASM_ENABLE_SHARED_HEAP
add wamrc --enable-shared-heap
consider the behavior of import memory in multi-module feature
adapt address conversion/validation
aot code boundary check
wasm_runtime_invoke_native
wasm_runtime_invoke_native_raw
wasm_runtime_validate_app_addrwasm_runtime_addr_app_to_nativewasm_runtime_addr_native_to_appwasm_runtime_validate_native_addrinterpreter/fast-jit do boundary check
classic interp modefast interp modejit
Support setting shared heap’s size and shared heap’s alloc options in RuntimeInitArgs for wasm_runtime_full_init
Add check in load module, default memory’s max_memory_size should be no larger than 4G-shared_heap_size, if not, reduce it to 4G-shared_heap_size
Add API wasm_runtime_shared_malloc/wasm_runtime_shared_free
App allocates memory from shared heap with API shared_malloc/shared_free
example
#3543
The text was updated successfully, but these errors were encountered: