Use "bounds" violation instead of "length" #367
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
This error also applies to access before the start of the capability, so length is not an accurate term, and most existing software already refers to it as a bounds violation. Fixes: riscv#366
jrtc27
reviewed
Sep 13, 2024
jrtc27
approved these changes
Sep 13, 2024
tariqkurd-repo
approved these changes
Sep 16, 2024
andresag01
approved these changes
Sep 16, 2024
tariqkurd-repo
pushed a commit
to tariqkurd-repo/riscv-cheri
that referenced
this pull request
Oct 9, 2024
This error also applies to access before the start of the capability, so length is not an accurate term, and most existing software already refers to it as a bounds violation. Fixes: riscv#366 --------- Co-authored-by: Andrés Amaya Garcia <andres.amaya@codasip.com>
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.
This error also applies to access before the start of the capability, so length is not an accurate term, and most existing software already refers to it as a bounds violation.
Fixes: #366