Implement analyzer checks for field size and offsets #86
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
DeltaEvo
approved these changes
Nov 11, 2023
hchataing
force-pushed
the
analyzer-size-checks
branch
2 times, most recently
from
a1d33d6 to
6c6b4aa
Compare
Validate that non-bitfield fields do start on an octet boundary, and that packet and structs have a size that is an integral number of octets. Fixes #33
hchataing
force-pushed
the
analyzer-size-checks
branch
from
6c6b4aa to
9a7ec23
Compare
|
Deprecated in favor of #114 |
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.
Validate that non-bitfield fields do start on an octet boundary,
and that packet and structs have a size that is an integral number
of octets.
Fixes #33