-
Notifications
You must be signed in to change notification settings - Fork 624
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
Make boundary check behavior configurable #2289
Conversation
what's the purpose of this? |
Let the wasm app access the host memory directly, in some application we bypass the libc to the host side, raw pointer from host maybe accessed in the wasm app. For this case, @wenyongh noticed that maybe we can implement https://github.com/WebAssembly/memory-control/blob/main/proposals/memory-control/Overview.md proposal. |
ok
the "preferred" option there is based on multi-memory. |
I'm investigating the possibility of it, this proposal is in early stage, and compiler also need to implement it. |
9d155fa
to
428e7dd
Compare
edefb64
to
2110f11
Compare
74e3cb9
to
05cb853
Compare
eb43da0
to
cd3b528
Compare
Change-Id: Id06b5f9f8b9ef4e29ed0bf70d9b48c5a70ea2853
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Works with bytecodealliance/wasm-micro-runtime#2289 Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
Works with bytecodealliance/wasm-micro-runtime#2289 Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
Works with bytecodealliance/wasm-micro-runtime#2289 Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
Works with bytecodealliance/wasm-micro-runtime#2289 Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
VELAPLATFO-10411 Works with bytecodealliance/wasm-micro-runtime#2289 Change-Id: I00308f799ab3e713d665df9a4d4077b51365776e Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
…ance#2289) Allow to use `cmake -DWAMR_CONFIGURABLE_BOUNDS_CHECKS=1` to build iwasm, and then run `iwasm --disable-bounds-checks` to disable the memory access boundary checks. And add two APIs: `wasm_runtime_set_bounds_checks` and `wasm_runtime_is_bounds_checks_enabled`
Notice: This is a non standard behavior, in this patch, boundary check can be disabled.
Known issues: