Disable static array-bounds check so suppress false positives #346
Conversation
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
Newer versions of GCC warn about memory accesses at non-zero offsets from null pointers. As we use this intentionally at different places in our code, these warnings result in many false positives. Temporarily, disabling the flag using pragmas is not viable as it is caused by macros that provide an expression. So we could not just fix the macro, but wherever it is used. Tracked by: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 Signed-off-by: Jean-Claude Graf <[email protected]>
jcjgraf
force-pushed
the
fix_array-bonds
branch
from
98af502 to
256cb24
Compare
wipawel
approved these changes
Dec 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Newer versions of GCC warn about memory accesses at non-zero offsets from null pointers. As we use this intentionally at different places in our code, these warnings result in many false positives. Temporarily, disabling the flag using pragmas is not viable as it is caused by macros that provide an expression. So we could not just fix the macro, but wherever it is used.
Tracked by: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578