User controlled stack boundary check in wamrc #3754
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wenyongh
approved these changes
Aug 28, 2024
…n boundary check is enabled
TianlongLiang
force-pushed
the
dev/wamrc_stack_bound_check
branch
from
bd9a039
to
000e687
Compare
LazyBoy-KK
pushed a commit
to LazyBoy-KK/wasm-micro-runtime
that referenced
this pull request
Oct 14, 2024
…ck is enabled (bytecodealliance#3754) In the AOT compiler, allow the user to control stack boundary check when the boundary check is enabled (e.g. `wamrc --bounds-checks=1`). Now the code logic is: 1. When `--stack-bounds-checks` is not set, it will be the same value as `--bounds-checks`. 2. When `--stack-bounds-checks` is set, it will be the option value no matter what the status of `--bounds-checks` is.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
wamrccompiler, allow the user to control stack boundary check when boundary check is enabled. Now the code logic is:--stack-bounds-checksis not set, it will be the same value as--bounds-checks.--stack-bounds-checksis set, it will be the option value no matter what the status of--bounds-checksis