-
Notifications
You must be signed in to change notification settings - Fork 55
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DeadCode
: Eliminate out-of-scope results, handle templates and multiple compilation
#717
base: main
Are you sure you want to change the base?
Conversation
Eliminate false positives where a line of code is used in some copies (instances) but not others.
Add a utility library for determing whether a condition holds for all copies of a statement in a program.
The modifications to the query to handle multiple copies of a statement across different targets also support reporting of issues across multiple template instantiations. This commit adds additional tests to demonstrate that this works effectively.
Ensure that macro expansions and multiple instances of code work together.
The rule description for this rule in fact talks about dead operations, not dead statements. Therefore: - Unshare the rule from MISRA C++ 2008 - Implement dead operation, as per the rule
Use the HoldsForAllInstances module to eliminate cases where a line of code is compiled into multiple targets with different dead code behaviour.
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.
Looks good to me! Basically just added some thoughts around language, almost entirely just comments.
* A module for considering whether a result occurs in all instances (e.g. copies) of the code at a | ||
* given location. | ||
*/ | ||
module HoldsForAllInstances<CandidateStmtSig CandidateStmt> { |
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, would it be better to name this HoldsForAllCopies?
) | ||
} | ||
|
||
/** A candidate set of types. */ |
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.
This comment could be elaborated, for instance, A statement type T that satisfies a relevant predicate, such that ``HoldsForAllInstances<T>::LogicalResultStmt`` points to _all_ copies of that statement iff all copies of that statement satisfy the relevant predicate as well
.
Oof, tricky to word the docs on this one! 😄
} | ||
|
||
/** | ||
* A logical result statement, representing all instances of a statement that occur at the same |
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.
Or something like, "The set of all statements that satisfy the predicate type CandidateStmtSig
, iff all copies of that statement also satisfy the relevant predicate."
cpp/common/src/codingstandards/cpp/alertreporting/HoldsForAllInstances.qll
Outdated
Show resolved
Hide resolved
1b10da8
to
6370722
Compare
Description
Fixes #716, #715 and #604:
RULE-2-2
is modified to match the rule text, now only reporting "operations" not statements.M0-1-9
andRULE-2-2
now handle cases where a line of code is compiled multiple times (e.g. templates, different targets), and has differing dead code states in each. We now only report a line of code as dead if it is dead in all instances.RULE-2-2
provides a better alert message.Change request type
.ql
,.qll
,.qls
or unit tests)Rules with added or modified queries
M0-1-9
RULE-2-2
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.