Misra C 2012 coverage

Total rules: 200

Number of implemented: 200

RuleTextCppcheck ID(s)
1.1The program shall contain no violations of the standard C syntax and constraints, and shall not exceed the implementation's translation limitssyntaxError
1.2Language extensions should not be usedmisra-c2012-1.2
1.3There shall be no occurrence of undefined or critical unspecified behaviourerror
1.4Emergent language features shall not be usedmisra-c2012-1.4
1.5Obsolescent language features shall not be usedmisra-c2012-1.5
2.1A project shall not contain unreachable codealwaysFalse
duplicateBreak
2.2There shall be no dead codealwaysTrue
redundantCondition
redundantAssignment
redundantAssignInSwitch
unreadVariable
2.3A project should not contain unused type declarationsmisra-c2012-2.3
2.4A project should not contain unused tag declarationsmisra-c2012-2.4
2.5A project should not contain unused macro declarationsmisra-c2012-2.5
2.6A function should not contain unused label declarationsunusedLabel
2.7A function should not contain unused parametersmisra-c2012-2.7
2.8A project should not contain unused object definitionsunusedVariable
3.1The character sequences /* and // shall not be used within a commentmisra-c2012-3.1
3.2Line-splicing shall not be used in // commentsmisra-c2012-3.2
4.1Octal and hexadecimal escape sequences shall be terminatedmisra-c2012-4.1
4.2Trigraphs should not be usedmisra-c2012-4.2
5.1External identifiers shall be distinctmisra-c2012-5.1
5.2Identifiers declared in the same scope and name space shall be distinctmisra-c2012-5.2
5.3An identifier declared in an inner scope shall not hide an identifier declared in an outer scopeshadowVariable
5.4Macro identifiers shall be distinctmisra-c2012-5.4
5.5Identifiers shall be distinct from macro namesmisra-c2012-5.5
5.6A typedef name shall be a unique identifiermisra-c2012-5.6
5.7A tag name shall be a unique identifiermisra-c2012-5.7
5.8Identifiers that define objects or functions with external linkage shall be uniquemisra-c2012-5.8
5.9Identifiers that define objects or functions with internal linkage should be uniquemisra-c2012-5.9
6.1Bit-fields shall only be declared with an appropriate typemisra-c2012-6.1
6.2Single-bit named bit fields shall not be of a signed typemisra-c2012-6.2
6.3A bit field shall not be declared as a member of a union.misra-c2012-6.3
7.1Octal constants shall not be usedmisra-c2012-7.1
7.2A "u" or "U" suffix shall be applied to all integer constants that are represented in an unsigned typemisra-c2012-7.2
7.3The lowercase character "l" shall not be used in a literal suffixmisra-c2012-7.3
7.4A string literal shall not be assigned to an object unless the object's type is "pointer to const-qualified char"misra-c2012-7.4
7.5The argument of an integer constant macro shall have an appropriate form.misra-c2012-7.5
7.6The small integer variants of the minimum-width integer constant macros shall not be usedmisra-c2012-7.6
8.1Types shall be explicitly specifiedmisra-c2012-8.1
8.2Function types shall be in prototype form with named parametersmisra-c2012-8.2
8.3All declarations of an object or function shall use the same names and type qualifiers.funcArgNamesDifferent
8.4A compatible declaration shall be visible when an object or function with external linkage is definedmisra-c2012-8.4
8.5An external object or function shall be declared once in one and only one filemisra-c2012-8.5
8.6An identifier with external linkage shall have exactly one external definitionmisra-c2012-8.6
8.7Functions and objects should not be defined with external linkage if they are referenced in only one translation unitmisra-c2012-8.7
8.8The static storage class specifier shall be used in all declarations of objects and functions that have internal linkagemisra-c2012-8.8
8.9An object should be defined at block scope if its identifier only appears in a single functionmisra-c2012-8.9
8.10An inline function shall be declared with the static storage classmisra-c2012-8.10
8.11When an array with external linkage is declared, its size should be explicitly specifiedmisra-c2012-8.11
8.12Within an enumerator list, the value of an implicitly-specified enumeration constant shall be uniquemisra-c2012-8.12
8.13A pointer should point to a const-qualified type whenever possibleconstParameterPointer
8.14The restrict type qualifier shall not be usedmisra-c2012-8.14
8.15All declarations of an object with an explicit alignment specification shall specify the same alignment.misra-c2012-8.15
8.16The alignment specification of zero should not appear in an object declaration.misra-c2012-8.16
8.17At most one explicit alignment specifier should appear in an object declaration.misra-c2012-8.17
9.1The value of an object with automatic storage duration shall not be read before it has been setuninitvar
9.2The initializer for an aggregate or union shall be enclosed in bracesmisra-c2012-9.2
9.3Arrays shall not be partially initializedmisra-c2012-9.3
9.4An element of an object shall not be initialized more than oncemisra-c2012-9.4
9.5Where designated initializers are used to initialize an array object the size of the array shall be specified explicitlymisra-c2012-9.5
9.6An initializer using chained designators shall not contain initializers without designatorsmisra-c2012-9.6
9.7Atomic objects shall be appropriately initialized before being accessedmisra-c2012-9.7
10.1Operands shall not be of an inappropriate essential type.misra-c2012-10.1
10.2Expressions of essentially character type shall not be used inappropriately in addition and subtraction operations.misra-c2012-10.2
10.3The value of an expression shall not be assigned to an object with a narrower essential type or of a different essential type category.misra-c2012-10.3
10.4Both operands of an operator in which the usual arithmetic conversions are performed shall have the same essential type category.misra-c2012-10.4
10.5The value of an expression should not be cast to an inappropriate essential type.misra-c2012-10.5
10.6The value of a composite expression shall not be assigned to an object with wider essential type.misra-c2012-10.6
10.7If a composite expression is used as one operand of an operator in which the usual arithmetic conversions are performed then the other operand shall not have wider essential type.misra-c2012-10.7
10.8The value of a composite expression shall not be cast to a different essential type category or a wider essential type.misra-c2012-10.8
11.1Conversions shall not be performed between a pointer to a function and any other typemisra-c2012-11.1
11.2Conversions shall not be performed between a pointer to an incomplete type and any other typemisra-c2012-11.2
11.3A cast shall not be performed between a pointer to object type and a pointer to a different object typemisra-c2012-11.3
11.4A conversion should not be performed between a pointer to object and an integer typemisra-c2012-11.4
11.5A conversion should not be performed from pointer to void into pointer to objectmisra-c2012-11.5
11.6A cast shall not be performed between pointer to void and an arithmetic typemisra-c2012-11.6
11.7A cast shall not be performed between pointer to object and a non-integer arithmetic typemisra-c2012-11.7
11.8A cast shall not remove any const or volatile qualification from the type pointed to by a pointermisra-c2012-11.8
11.9The macro NULL shall be the only permitted form of integer null pointer constantmisra-c2012-11.9
11.10The _Atomic qualifier shall not be applied to the incomplete type voidmisra-c2012-11.10
12.1The precedence of operators within expressions should be made explicitmisra-c2012-12.1
12.2The right hand operand of a shift operator shall lie in the range zero to one less than the width in bits of the essential type of the left hand operandmisra-c2012-12.2
12.3The comma operator should not be used.sizeofwithsilentarraypointer
12.4Evaluation of constant expressions should not lead to unsigned integer wrap-aroundmisra-c2012-12.4
12.5The sizeof operator shall not have an operand which is a function parameter declared as "array of type"misra-c2012-12.5
12.6Structure and union members of atomic objects shall not be directly accessedmisra-c2012-12.6
13.1Initializer lists shall not contain persistent side effects.misra-c2012-13.1
13.2The value of an expression and its persistent side effects shall be the same under all permitted evaluation orders and shall be independent from thread interleaving.unknownEvaluationOrder
13.3A full expression containing an increment (++) or decrement (--) operator should have no other potential side effects other than that caused by the increment or decrement operator.misra-c2012-13.3
13.4The result of an assignment operator should not be used.misra-c2012-13.4
13.5The right hand operand of a logical && or || operator shall not contain persistent side effects.misra-c2012-13.5
13.6The operand of the sizeof operator shall not contain any expression which has potential side effects.sizeofCalculation
14.1A loop counter shall not have essentially floating typemisra-c2012-14.1
14.2A for loop shall be well-formedmisra-c2012-14.2
14.3Controlling expressions shall not be invariantalwaysTrue
alwaysFalse
compareValueOutOfTypeRangeError
knownConditionTrueFalse
14.4The controlling expression of an if statement and the controlling expression of an iteration-statement shall have essentially Boolean typemisra-c2012-14.4
15.1The goto statement should not be usedmisra-c2012-15.1
15.2The goto statement shall jump to a label declared later in the same functionmisra-c2012-15.2
15.3Any label referenced by a goto statement shall be declared in the same block, or in any block enclosing the goto statementmisra-c2012-15.3
15.4There should be no more than one break or goto statement used to terminate any iteration statementmisra-c2012-15.4
15.5A function should have a single point of exit at the end.misra-c2012-15.5
15.6The body of an iteration-statement or a selection-statement shall be a compound-statementmisra-c2012-15.6
15.7All if ... else if constructs shall be terminated with an else statementmisra-c2012-15.7
16.1All switch statements shall be well-formedmisra-c2012-16.1
16.2A switch label shall only be used when the most closely-enclosing compound statement is the body of a switch statementmisra-c2012-16.2
16.3An unconditional break statement shall terminate every switch-clause.misra-c2012-16.3
16.4Every switch statement shall have a default labelmisra-c2012-16.4
16.5A default label shall appear as either the first or the last switch label of a switch statementmisra-c2012-16.5
16.6Every switch statement shall have at least two switch-clausesmisra-c2012-16.6
16.7A switch-expression shall not have essentially Boolean typemisra-c2012-16.7
17.1The features of <stdarg.h> shall not be usedmisra-c2012-17.1
17.2Functions shall not call themselves, either directly or indirectlymisra-c2012-17.2
17.3A function shall not be declared implicitly.misra-c2012-17.3
17.4All exit paths from a function with non-void return type shall have an explicit return statement with an expressionmissingReturn
17.5The function argument corresponding to a parameter declared to have an array type shall have an appropriate number of elementsargumentSize
17.6The declaration of an array parameter shall not contain the static keyword between the [ ]misra-c2012-17.6
17.7The value returned by a function having non-void return type shall be usedmisra-c2012-17.7
17.8A function parameter should not be modifiedmisra-c2012-17.8
17.9A function declared with a _Noreturn function specifier shall not return to its caller.misra-c2012-17.9
17.10A function declared with a _Noreturn function specifier shall have void return type.misra-c2012-17.10
17.11A function that never returns should be declared with a _Noreturn function specifier.misra-c2012-17.11
17.12A function identifier should only be used with either a preceding &, or with a parenthesized parameter list.misra-c2012-17.12
17.13A function type shall not be type qualifiedmisra-c2012-17.13
18.1A pointer resulting from arithmetic on a pointer operand shall address an element of the same array as that pointer operandpointerOutOfBounds
18.2Subtraction between pointers shall only be applied to pointers that address elements of the same arraycomparePointers
18.3The relational operators >, >=, < and <= shall not be applied to objects of pointer type except where they point into the same objectcomparePointers
18.4The +, -, += and -= operators should not be applied to an expression of pointer typemisra-c2012-18.4
18.5Declarations should contain no more than two levels of pointer nesting.misra-c2012-18.5
18.6The address of an object with automatic storage shall not be copied to another object that persists after the first object has ceased to existdanglingLifetime
danglingTemporaryLifetime
returnDanglingLifetime
18.7Flexible array members shall not be declaredmisra-c2012-18.7
18.8Variable-length array types shall not be used.misra-c2012-18.8
18.9An object with temporary lifetime shall not undergo array-to-pointer conversion.misra-c2012-18.9
18.10Pointers to variably-modified array types shall not be usedmisra-c2012-18.10
19.1An object shall not be assigned or copied to an overlapping objectoverlappingWriteUnion
overlappingWriteFunction
19.2The union keyword should not be usedmisra-c2012-19.2
20.1#include directives should only be preceded by preprocessor directives or commentsmisra-c2012-20.1
20.2The ', " or \ characters and the /* or // character sequences shall not occur in a header file namemisra-c2012-20.2
20.3The #include directive shall be followed by either a <filename> or \"filename\" sequence.misra-c2012-20.3
20.4A macro shall not be defined with the same name as a keywordmisra-c2012-20.4
20.5#undef should not be usedmisra-c2012-20.5
20.6Tokens that look like a preprocessing directive shall not occur within a macro argumentpreprocessorErrorDirective
20.7Expressions resulting from the expansion of macro parameters shall be enclosed in parenthesesmisra-c2012-20.7
20.8The controlling expression of a #if or #elif preprocessing directive shall evaluate to 0 or 1misra-c2012-20.8
20.9All identifiers used in the controlling expression of #if or #elif preprocessing directives shall be #define'd before evaluationmisra-c2012-20.9
20.10The # and ## preprocessor operators should not be usedmisra-c2012-20.10
20.11A macro parameter immediately following a # operator shall not immediately be followed by a ## operatormisra-c2012-20.11
20.12A macro parameter used as an operand to the # or ## operators, which is itself subject to further macro replacement, shall only be used as an operand to these operatorsmisra-c2012-20.12
20.13A line whose first token is # shall be a valid preprocessing directivemisra-c2012-20.13
20.14All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if, #ifdef or #ifndef directive to which they are relatedmisra-c2012-20.14
21.1#define and #undef shall not be used on a reserved identifier or reserved macro name.misra-c2012-21.1
21.2A reserved identifier or reserved macro name shall not be declared.misra-c2012-21.2
21.3The memory allocation and deallocation functions of <stdlib.h> shall not be usedmisra-c2012-21.3
21.4The standard header file <setjmp.h> shall not be usedmisra-c2012-21.4
21.5The standard header file <signal.h> shall not be usedmisra-c2012-21.5
21.6The Standard Library input/output functions shall not be usedmisra-c2012-21.6
21.7The atof, atoi, atol and atoll functions of <stdlib.h> shall not be usedmisra-c2012-21.7
21.8The library functions abort, exit, getenv and system of <stdlib.h> shall not be usedmisra-c2012-21.8
21.9The library functions bsearch and qsort of <stdlib.h> shall not be usedmisra-c2012-21.9
21.10The Standard Library time and date functions shall not be usedmisra-c2012-21.10
21.11The standard header file <tgmath.h> shall not be usedmisra-c2012-21.11
21.12The standard header file <fenv.h> shall not be used.misra-c2012-21.12
21.13Any value passed to a function in <ctype.h> shall be representable as an unsigned char or be the value EOFinvalidFunctionArg
21.14The Standard Library function memcmp shall not be used to compare null terminated stringsmisra-c2012-21.14
21.15The pointer arguments to the Standard Library functions memcpy, memmove and memcmp shall be pointers to qualified or unqualified versions of compatible typesmisra-c2012-21.15
21.16The pointer arguments to the Standard Library function memcmp shall point to either a pointer type, an essentially signed type, an essentially unsigned type, an essentially Boolean type or an essentially enum type.misra-c2012-21.16
21.17Use of the string handling functions from <string.h> shall not result in accesses beyond the bounds of the objects referenced by their pointer parametersbufferAccessOutOfBounds
21.18The size_t argument passed to any function in <string.h> shall have an appropriate valuebufferAccessOutOfBounds
21.19The pointers returned by the Standard Library functions localeconv, getenv, setlocale or, strerror shall only be used as if they have pointer to const-qualified typemisra-c2012-21.19
21.20The pointer returned by the Standard Library functions asctime, ctime, gmtime, localtime, localeconv, getenv, setlocale or strerror shall not be used following a subsequent call to the same functionmisra-c2012-21.20
21.21The standard library function system of <stdlib.h> shall not be usedmisra-c2012-21.21
21.22All operand arguments to any type-generic macros declared in <tgmath.h> shall have an appropriate essential type. sqrt() has a non-arithmetic type of argument 'p1'misra-c2012-21.22
21.23All operand arguments to any multi-argument type-generic macros declared in <tgmath.h> shall have the same standard type.misra-c2012-21.23
21.24The random number generator functions of <stdlib.h> shall not be used. Calling rand()misra-c2012-21.24
21.25All memory synchronization operations shall be executed in sequentially consistent ordermisra-c2012-21.25
21.26The Standard Library function mtx_timedlock() shall only be invoked on mutex objects of appropriate mutex typemisra-c2012-21.26
22.1All resources obtained dynamically by means of Standard Library functions shall be explicitly releasedmemleak
resourceLeak
memleakOnRealloc
leakReturnValNotUsed
leakNoVarFunctionCall
22.2A block of memory shall only be freed if it was allocated by means of a Standard Library functionautovarInvalidDeallocation
22.3The same file shall not be open for read and write access at the same time on different streamsincompatibleFileOpen
22.4There shall be no attempt to write to a stream which has been opened as read-onlywriteReadOnlyFile
22.5A pointer to a FILE object shall not be dereferencedmisra-c2012-22.5
22.6The value of a pointer to a FILE shall not be used after the associated stream has been closeduseClosedFile
22.7The macro EOF shall only be compared with the unmodified return value from any Standard Library function capable of returning EOFmisra-c2012-22.7
22.8The value of errno shall be set to zero prior to a call to an errno-setting-functionmisra-c2012-22.8
22.9The value of errno shall be tested against zero after calling an errno-setting-functionmisra-c2012-22.9
22.10The value of errno shall only be tested when the last function to be called was an errno-setting-functionmisra-c2012-22.10
22.11A thread that was previously either joined or detached shall not be subsequently joined nor detachedmisra-c2012-22.11
22.12Thread objects, thread synchronization objects, and thread-specific storage pointers shall only be accessed by the appropriate Standard Library functionsmisra-c2012-22.12
22.13Thread objects, thread synchronization objects and thread-specific storage pointers shall have appropriate storage durationmisra-c2012-22.13
22.14Thread synchronization objects shall be initialized before being accessedmisra-c2012-22.14
22.15Thread synchronization objects and thread-specific storage pointers shall not be destroyed until after all threads accessing them have terminatedmisra-c2012-22.15
22.16All mutex objects locked by a thread shall be explicitly unlocked by the same threadmisra-c2012-22.16
22.17No thread shall unlock a mutex or call cnd_wait() or cnd_timedwait() for a mutex it has not locked beforemisra-c2012-22.17
22.18Non-recursive mutexes shall not be recursively lockedmisra-c2012-22.18
22.19A condition variable shall be associated with at most one mutex objectmisra-c2012-22.19
22.20Thread-specific storage pointers shall be created before being accessedmisra-c2012-22.20
23.1A generic selection should only be expanded from a macro.misra-c2012-23.1
23.2A generic selection that is not expanded from a macro shall not contain potential side effects in the controlling expression.misra-c2012-23.2
23.3A generic selection should contain at least one non-default association.misra-c2012-23.3
23.4A generic association shall list an appropriate type.misra-c2012-23.4
23.5A generic selection should not depend on implicit pointer type conversion.misra-c2012-23.5
23.6The controlling expression of a generic selection shall have an essential type that matches its standard type.misra-c2012-23.6
23.7A generic selection that is expanded from a macro should evaluate its argument only once.misra-c2012-23.7
23.8A default association shall appear as either the first or the last association of a generic selection.misra-c2012-23.8