Fix htool security v2 comand to avoid strict aliasing violations#274
Merged
Conversation
willyzha
force-pushed
the
fix-strict-aliasing
branch
from
4cc2e8c to
10c9f2e
Compare
cjevans-google
approved these changes
Jun 15, 2026
This eliminates the need for unsafe type casts, (uint8_t**)¶m, which violates strict aliasing rules and can lead to compiler optimizations that incorrectly assume pointers are not modified (leaving them as NULL).
willyzha
force-pushed
the
fix-strict-aliasing
branch
from
10c9f2e to
5810771
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
3 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 eliminates the need for unsafe type casts, (uint8_t**)¶m, which violates strict aliasing rules and can lead to compiler optimizations that incorrectly assume pointers are not modified (leaving them as NULL).