Übersicht, Preise,
Bestellen u.m.

PC-Lint / FlexeLint für C/C++ -
Kontrolle des Misra-C Standards

MISRA (Motor Industrie Software Reliability Association) hat unter dem Titel
Guidelines for the Use of the C Language in Vehicle Based Software
Regeln zur C Programmierung formuliert.
Mit PC-Lint / FlexeLint kann sichergestellt werden, daß der MISRA-C Standard eingehalten wird,
soweit dies mit statischer Analyse möglich ist.
Es wird Misra-2, aber auch noch Misra-1 unterstützt.
Die Lint Meldungen 960 und 961 liefern die Details:

960 Violates MISRA Year Required Rule Name, String
-- MISRA is the"Guidelines for the use of the C Language in Vehicle Based Software". [9, 33] The first version of the MISRA Standard was released in 1998 and the second in 2004. Lint refers to the rules below in the form:
Rule I/D
where I is an integer rule number from the 1998 Standard and D is a decimal rule number from the 2004 Standard. When issuing messages, Lint will refer to the rules using the form:
Rule I - for the 1998 Standard and the form:
Rule D - for the 2004 Standard.

The list of required checks made for both MISRA 1998 and 2004 are:
(Rule 19/7.1) Octal constant used.
(Rule 32/9.3) Should initialize either all enum members or only the first.
(Rule 33/12.4) Side effects on right hand side of logical operator.
(Rule 42/12.10) Rule Comma operator used outside of 'for' expression.
(Rule 54/14.3) Null statement not in line by itself.
(Rule 57/14.5) continue statement should not be used.
(Rules 59/14.8 & 14.9) Left brace expected for if, else, for, do, and while.
(Rule 65/13.4) Floating point variable used as loop counter.
(Rule 68/8.6) Function not declared at file scope.
(Rule 69/16.1) Function has variable number of arguments.
(Rule 73/16.3) Either all parameters or no parameters should have identifiers.
(Rule 91/19.5 '#define/#undef' used within a block (Rule 91/19.5).
(Rule 98/19.12) Multiple use of '#' and/or '##' operators in macro definition.
(Rule 100/19.14) Non-standard use of 'defined' preprocessor operator.

Required checks made exclusively for MISRA 1998 are:
(Rule 58) break used outside of a switch.
(Rule 88) Header file name contains non-standard non-standard character.
(Rule 110) Bitfields inside union.

Required checks made exclusively for MISRA 2004 are:
(Rule 8.5) No definitions of objects or function in header files.
(Rules 10.1 & 10.2) Prohibited implicit conversion.
(Rules 10.3 & 10.4) Prohibited cast of complex expressions.
(Rule 10.5) Recasting required for operators '~' and '<<'.
(Rule 12.3) 'sizeof' used on expressions with side effect.
(Rule 12.7) Bitwise operator applied to signed underlying type.
(Rule 12.9) Prohibited operator applied to unsigned underlying type.
(Rule 14.6) More than one 'break' terminates loop.
(Rule 14.10) No 'else' at end of 'if ... else if' chain.
(Rule 15.4) Boolean value in switch expression.
(Rule 18.4) Unions shall not be used.
(Rule 19.6) Use of '#undef' prohibited.

MISRA 1998 checking is achieved using the -misra(1) option.
For MISRA 2004 checks, use -misra(2).
You may disable individual rules to your taste by using the Rule number in an esym option.
For example: -esym( 960, 75, 8? )
will suppress MISRA rules 75 and any of the those between 80 and 89 inclusive that are issued as the result of a 960. See [33, 34] for information on the MISRA guidelines

961 Violates MISRA Year Advisory RuleName, String

-- This message is issued for some violations of the MISRA advisory guidelines. Certain rules were advisories in the
1998 Standard and became required for the 2004 Standard and vice versa. Therefore, you might see some rules repeated here already listed above for message 960.

The list of advisory checks made for both MISRA 1998 and 2004 are:
(Rule 47/12.1) Dependence placed on C's operator precedence.
(Rule 87.19.1) Only preprocessor statements and comments before '#include'.
(Rule 93/19.7) Use of function-like macros is discouraged.
(Rule102)17.5) More than two pointer indirection levels used.

Advisory checks made exclusively for MISRA 1998 are:
(Rule 18) Constant requires numerical suffix.
(Rule 28) 'register' class discouraged.
(Rule 40) 'sizeof' used on expressions with side effect.(Rule 44 ) Redundant explicit casting.
(Rule 55) Non-case label.
(Rule 60) No 'else' at end of 'if ... else if' chain.
(Rule 63) Boolean value in switch expression.
(Rule 92) Use of '#undef' is discouraged.

Advisory checks made exclusively for MISRA 2004 are:
(Rule 19.2) Header file name contains non-standard non-standard character.
(Rule 19.13) No use of '#' or '##'.

Messages can be suppressed based on rule number. See also Message 960.