New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rule 11.4 improvements #332
base: main
Are you sure you want to change the base?
Conversation
According to MISRA C 2012 8.11 zero is a null pointer constant, and so should not be flagged as non_compliant.
Where results arise from macro expansions, where there's no possibility that the cast was passed in through a macro argument, we compress the results by reporting the macro location once instead of each use.
Improve the message by (a) reporting which order the cast is (b) what the actual types are (c) by providing a link to the macro invocation if the cast is created by a function like macro
e instanceof Zero and | ||
c.getType() instanceof VoidPointerType | ||
) | ||
e instanceof Zero |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self: this affects Rule 11.9, which is incorrect. 0
is a null pointer constant, but not permitted according to 11.9.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add this comment to the changenote (if it changes the result of Rule 11.9)
@@ -0,0 +1,4 @@ | |||
- `RULE-11-4` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- `RULE-11-4` | |
- `RULE-11-4` - `ConversionBetweenPointerToObjectAndIntegerType.ql`: | |
- Fixed issue #331 - consider `0` a null pointer constant. |
@@ -0,0 +1,4 @@ | |||
- `RULE-11-4` | |||
- Reduce false positives by considering `0` a null pointer constant. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Reduce false positives by considering `0` a null pointer constant. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comments only, otherwise looks good! @lcartey
needs a merge resolve,
and I think you accidentally marked the reviewer's checkboxes , not the author's ones, I agree with the completion of those, but please also mark the author ones!
Description
This pull request makes the following improvements to the query for Rule 11.4:
0
to be a null pointer constant (fixesRULE-11-4
: Consider0
to be a null pointer constant.聽#331).Change request type
.ql
,.qll
,.qls
or unit tests)Rules with added or modified queries
RULE-11-4
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
馃毃馃毃馃毃
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.