As I see it Cppcheck and the misra addon and some help from gcc, now has coverage of all the original misra c2012 rules.
there are currently 3 rules not covered by Cppcheck and the misra addon:
1.1, 1.2, 17.3
the rules 1.1 and 1.2 will never be covered I think users will have to rely on their compiler (or gcc) for those.
the rule 17.3 is tricky because we don't want to include system headers in cppcheck analysis.. but gcc has corresponding diagnostics (-Wimplicit-function-declaration). For now gcc must be used for rule 17.3.
I plan to implement the misra c2012 amendments later also.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I see it Cppcheck and the misra addon and some help from gcc, now has coverage of all the original misra c2012 rules.
there are currently 3 rules not covered by Cppcheck and the misra addon:
1.1, 1.2, 17.3
the rules 1.1 and 1.2 will never be covered I think users will have to rely on their compiler (or gcc) for those.
the rule 17.3 is tricky because we don't want to include system headers in cppcheck analysis.. but gcc has corresponding diagnostics (-Wimplicit-function-declaration). For now gcc must be used for rule 17.3.
I plan to implement the misra c2012 amendments later also.
As you probably know.. you can use
python3 misra.py -generate-table
to see if a rule is covered by Cppcheck or if it is covered by the addon.