Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Rule 1.3 - What do people do to check this rule?
Andrew Banks Wrote:Appendix H.1 lists the Undefined Behaviours

Of the 61 you mention, 46 are Decidable and are of the form "X is undefined" - we decided that 46 rules of the form "Don't use undefined behaviour X" was unnecessary duplication of the generic "Don't use undefined behaviour". A tool that detects the UB will detect them under Rule 1.3 even where other Rules are not specified.

Of the remaining 19 undecidable behaviours, nine are partially addressed by other MISRA C rules... tools may also detect these under Rule 1.3

If, however, you are not using a tool, then a manual code review will need to detect the UB under Rule 1.3, whether there are specific additional MISRA C rules or not!

How about unspecified behaviors?
there are 50 unspecified behaviors in C99, and there is no 'decidable' field in Appendix H, MISRA C:2012.

In Appendix H, some 'Id' are written with 'Guidelines' but 17 Ids are not. i mean no entry in Guidelines field.
are the 17 unspecified behaviors avoided by rule 1.3? or not?

Messages In This Thread

Forum Jump:

Users browsing this thread: 1 Guest(s)