AArch64 bitfieldManipulate bounds checking#395
Merged
Conversation
jj16791
requested review from
ABenC377,
FinnWilkinson,
JosephMoore25 and
dANW34V3R
FinnWilkinson
added
0.9.6
jj16791
commented
Feb 21, 2024
ABenC377
previously approved these changes
Feb 21, 2024
FinnWilkinson
approved these changes
Feb 21, 2024
JosephMoore25
approved these changes
Feb 21, 2024
dANW34V3R
approved these changes
Feb 21, 2024
ABenC377
approved these changes
Feb 21, 2024
Contributor
|
#rerun tests |
jj16791
force-pushed
the
bitfieldManipulate-boundsFix
branch
from
f4e3419 to
1ac04e4
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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 PR addresses the issue that bitfieldManipulate has no bounds checking/restriction enforced by the data type in use.
close #394