Overview
The MISRA (Motor Industry Software Reliability Association) guidance is a software development standards that was created to facilitate best practices for programming safety-critical software in road vehicles and other embedded systems.
Relevant Warning Classes
The following accordion shows the CodeSonar warning classes that are associated with MISRA security rules.
Mapping Definition
The table below show classes from our broad mapping which for a given warning class and category kind combines categories from four sources:
- The close mapping for the class.
- Other categories of that kind that are related to the class in a meaningful way, but not eligible for the close mapping. Usually this indicates a substantial overlap between category and warning class, but overlap that cannot be characterized as a subset or superset relationship.
- It the category kind is hierarchical (of the current category taxonomies, only We has this property): tor all categories trom sources 1 and 2, all ancestors in the taxonomy hierarchy
- In a small number of cases, all descendants of a hierarchical category source 1 or 2 are also applicable to the class. In these cases the descendants are also added to the broad mapping
MISRA 2004
Mapping Summary
| Supported | All | Percent Coverage | |
|---|---|---|---|
| All | 122 | 142 | 85.9% |
| Required | 106 | 122 | 86.9% |
| Advisory | 16 | 20 | 80.0% |
Mapping Detail
| Rule | Rule Name | Category | Supported |
|---|---|---|---|
| Misra2004:1.1 | All code shall conform to ISO/IEC 9899:1990 "Programming languages C", amended and corrected by ISO/IEC 9899/COR1:1995, ISO/IEC 9899/AMD1:1995, and ISO/IEC 9899/COR2:1996 | Required | Yes |
| Misra2004:1.2 | No reliance shall be placed on undefined or unspecified behaviour | Required | Yes |
| Misra2004:1.3 | Multiple compilers and/or languages shall only be used if there is a common defined interface standard for object code to which the languages/compilers/assemblers conform | Required | No |
| Misra2004:1.4 | The compiler/linker shall be checked to ensure that 31 character significance and case sensitivity are supported for external identifiers | Required | No |
| Misra2004:1.5 | Floating-point implementations should comply with a defined floating-point standard | Advisory | No |
| Misra2004:2.1 | Assembly language shall be encapsulated and isolated | Required | Yes |
| Misra2004:2.2 | Source code shall only use /* ... */ style comments | Required | Yes |
| Misra2004:2.3 | The character sequence /* shall not be used within a comment | Required | Yes |
| Misra2004:2.4 | Sections of code should not be "commented out" | Advisory | Yes |
| Misra2004:3.1 | All usage of implementation-defined behaviour shall be documented | Required | No |
| Misra2004:3.2 | The character set and the corresponding encoding shall be documented | Required | No |
| Misra2004:3.3 | The implementation of integer division in the chosen compiler should be determined, documented and taken into account | Advisory | No |
| Misra2004:3.4 | All uses of the #pragma directive shall be documented and explained | Required | Yes |
| Misra2004:3.5 | The implementation defined behaviour and packing of bitfields shall be documented if being relied upon | Required | Yes |
| Misra2004:3.6 | All libraries used in production code shall be written to comply with the provisions of this document, and shall have been subject to appropriate validation | Required | No |
| Misra2004:4.1 | Only those escape sequences that are defined in the ISO C standard shall be used | Required | No |
| Misra2004:4.2 | Trigraphs shall not be used | Required | Yes |
| Misra2004:5.1 | Identifiers (internal and external) shall not rely on the significance of more than 31 characters | Required | Yes |
| Misra2004:5.2 | Identifiers in an inner scope shall not use the same name as an identifier in an outer scope, and therefore hide that identifier | Required | Yes |
| Misra2004:5.3 | A typedef name shall be a unique identifier | Required | Yes |
| Misra2004:5.4 | A tag name shall be a unique identifier | Required | Yes |
| Misra2004:5.5 | No object or function identifier with static storage duration should be reused | Advisory | Yes |
| Misra2004:5.6 | No identifier in one name space should have the same spelling as an identifier in another name space, with the exception of structure member and union member names | Advisory | No |
| Misra2004:5.7 | No identifier name should be reused | Advisory | Yes |
| Misra2004:6.1 | The plain char type shall be used only for storage and use of character values | Required | Yes |
| Misra2004:6.2 | signed and unsigned char type shall be used only for the storage and use of numeric values | Required | Yes |
| Misra2004:6.3 | typedefs that indicate size and signedness should be used in place of the basic numerical types | Advisory | Yes |
| Misra2004:6.4 | Bit fields shall only be defined to be of type unsigned int or signed int | Required | Yes |
| Misra2004:6.5 | Bit fields of signed type shall be at least 2 bits long | Required | Yes |
| Misra2004:7.1 | Octal constants (other than zero) and octal escape sequences shall not be used | Required | Yes |
| Misra2004:8.1 | Functions shall have prototype declarations and the prototype shall be visible at both the function definition and call | Required | Yes |
| Misra2004:8.2 | Whenever an object or function is declared or defined, its type shall be explicitly stated | Required | Yes |
| Misra2004:8.3 | For each function parameter the type given in the declaration and definition shall be identical, and the return types shall also be identical | Required | Yes |
| Misra2004:8.4 | If objects or functions are declared more than once their types shall be compatible | Required | Yes |
| Misra2004:8.5 | There shall be no definitions of objects or functions in a header file | Required | Yes |
| Misra2004:8.6 | Functions shall be declared at file scope | Required | Yes |
| Misra2004:8.7 | Objects shall be defined at block scope if they are only accessed from within a single function | Required | Yes |
| Misra2004:8.8 | An external object or function shall be declared in one and only one file | Required | Yes |
| Misra2004:8.9 | An identifier with external linkage shall have exactly one external definition | Required | Yes |
| Misra2004:8.10 | All declarations and definitions of objects or functions at file scope shall have internal linkage unless external linkage is required | Required | Yes |
| Misra2004:8.11 | The static storage class specifier shall be used in definitions and declarations of objects and functions that have internal linkage | Required | Yes |
| Misra2004:8.12 | When an array is declared with external linkage, its size shall be stated explicitly or defined implicitly by initialisation | Required | Yes |
| Misra2004:9.1 | All automatic variables shall have been assigned a value before being used | Required | Yes |
| Misra2004:9.2 | Braces shall be used to indicate and match the structure in the non-zero initialisation of arrays and structures | Required | Yes |
| Misra2004:9.3 | In an enumerator list, the "=" construct shall not be used to explicitly initialise members other than the first, unless all items are explicitly initialised | Required | Yes |
| Misra2004:10.1 | The value of an expression of integer type shall not be implicitly converted to a different underlying type if: (a) it is not a conversion to a wider integer type of the same signedness, or (b) the expression is complex, or (c) the expression is not constant and is a function argument, or (d) the expression is not constant and is a return expression | Required | Yes |
| Misra2004:10.2 | The value of an expression of floating type shall not be implicitly converted to a different type if: (a) it is not a conversion to a wider floating type, or (b) the expression is complex, or (c) the expression is a function argument, or (d) the expression is a return expression | Required | Yes |
| Misra2004:10.3 | The value of a complex expression of integer type shall only be cast to a type of the same signedness that is no wider than the underlying type of the expression | Required | Yes |
| Misra2004:10.4 | The value of a complex expression of floating type shall only be cast to a floating type that is narrower or of the same size | Required | Yes |
| Misra2004:10.5 | If the bitwise operators ~ and <></> | Required | Yes |
| Misra2004:10.6 | A "U" suffix shall be applied to all constants of unsigned type | Required | Yes |
| Misra2004:11.1 | Conversions shall not be performed between a pointer to a function and any type other than an integral type | Required | Yes |
| Misra2004:11.2 | Conversions shall not be performed between a pointer to object and any type other than an integral type, another pointer to object type or a pointer to void | Required | Yes |
| Misra2004:11.3 | A cast should not be performed between a pointer type and an integral type | Advisory | Yes |
| Misra2004:11.4 | A cast should not be performed between a pointer to object type and a different pointer to object type | Advisory | Yes |
| Misra2004:11.5 | A cast shall not be performed that removes any const or volatile qualification from the type addressed by a pointer | Required | Yes |
| Misra2004:12.1 | Limited dependence should be placed on C's operator precedence rules in expressions | Advisory | Yes |
| Misra2004:12.2 | The value of an expression shall be the same under any order of evaluation that the standard permits | Required | Yes |
| Misra2004:12.3 | The sizeof operator shall not be used on expressions that contain side effects | Required | Yes |
| Misra2004:12.4 | The right-hand operand of a logical && or || operator shall not contain side effects | Required | Yes |
| Misra2004:12.5 | The operands of a logical && or || shall be primary-expressions | Required | No |
| Misra2004:12.6 | The operands of logical operators (&&, || and !) should be effectively Boolean. Expressions that are effectively Boolean should not be used as operands to operators other than (&&, || , !, =, ==, != and ?:) | Advisory | Yes |
| Misra2004:12.7 | Bitwise operators shall not be applied to operands whose underlying type is signed | Required | Yes |
| Misra2004:12.8 | The right-hand operand of a shift operator shall lie between zero and one less than the width in bits of the underlying type of the left-hand operand | Required | Yes |
| Misra2004:12.9 | The unary minus operator shall not be applied to an expression whose underlying type is unsigned | Required | Yes |
| Misra2004:12.10 | The comma operator shall not be used | Required | Yes |
| Misra2004:12.11 | Evaluation of constant unsigned integer expressions should not lead to wraparound | Advisory | Yes |
| Misra2004:12.12 | The underlying bit representations of floating-point values shall not be used | Required | Yes |
| Misra2004:12.13 | The increment (++) and decrement (--) operators should not be mixed with other operators in an expression | Advisory | Yes |
| Misra2004:13.1 | Assignment operators shall not be used in expressions that yield a Boolean value | Required | Yes |
| Misra2004:13.2 | Tests of a value against zero should be made explicit, unless the operand is effectively Boolean | Advisory | Yes |
| Misra2004:13.3 | Floating-point expressions shall not be tested for equality or inequality | Required | Yes |
| Misra2004:13.4 | The controlling expression of a for statement shall not contain any objects of floating type | Required | Yes |
| Misra2004:13.5 | The three expressions of a for statement shall be concerned only with loop control | Required | Yes |
| Misra2004:13.6 | Numeric variables being used within a for loop for iteration counting shall not be modified in the body of the loop | Required | Yes |
| Misra2004:13.7 | Boolean operations whose results are invariant shall not be permitted | Required | Yes |
| Misra2004:14.1 | There shall be no unreachable code | Required | Yes |
| Misra2004:14.2 | All non-null statements shall either (a) have at least one side-effect however executed, or (b) cause control flow to change | Required | Yes |
| Misra2004:14.3 | Before preprocessing, a null statement shall only occur on a line by itself; it may be followed by a comment provided that the first character following the null statement is a white-space character | Required | Yes |
| Misra2004:14.4 | The goto statement shall not be used | Required | Yes |
| Misra2004:14.5 | The continue statement shall not be used | Required | Yes |
| Misra2004:14.6 | For any iteration statement there shall be at most one break statement used for loop termination | Required | Yes |
| Misra2004:14.7 | A function shall have a single point of exit at the end of the function | Required | Yes |
| Misra2004:14.8 | The statement forming the body of a switch, while, do ... while or for statement shall be a compound statement | Required | Yes |
| Misra2004:14.9 | An if (expression) construct shall be followed by a compound statement. The else keyword shall be followed by either a compound statement, or another if statement | Required | Yes |
| Misra2004:14.10 | All if . else if constructs shall be terminated with an else clause | Required | Yes |
| Misra2004:15.0 | The MISRA C switch syntax shall be used | Required | Yes |
| Misra2004:15.1 | A switch label shall only be used when the most closely-enclosing compound statement is the body of a switch statement | Required | Yes |
| Misra2004:15.2 | An unconditional break statement shall terminate every non-empty switch clause | Required | Yes |
| Misra2004:15.3 | The final clause of a switch statement shall be the default clause | Required | Yes |
| Misra2004:15.4 | A switch expression shall not represent a value that is effectively Boolean | Required | Yes |
| Misra2004:15.5 | Every switch statement shall have at least one case clause | Required | Yes |
| Misra2004:16.1 | Functions shall not be defined with variable numbers of arguments | Required | Yes |
| Misra2004:16.2 | Functions shall not call themselves, either directly or indirectly | Required | Yes |
| Misra2004:16.3 | Identifiers shall be given for all of the parameters in a function prototype declaration | Required | Yes |
| Misra2004:16.4 | The identifiers used in the declaration and definition of a function shall be identical | Required | Yes |
| Misra2004:16.5 | Functions with no parameters shall be declared and defined with the parameter list void | Required | Yes |
| Misra2004:16.6 | The number of arguments passed to a function shall match the number of parameters | Required | Yes |
| Misra2004:16.7 | A pointer parameter in a function prototype should be declared as pointer to const if the pointer is not used to modify the addressed object | Advisory | Yes |
| Misra2004:16.8 | All exit paths from a function with non-void return type shall have an explicit return statement with an expression | Required | Yes |
| Misra2004:16.9 | A function identifier shall only be used with either a preceding &, or with a parenthesised parameter list, which may be empty | Required | Yes |
| Misra2004:16.10 | If a function returns error information, then that error information shall be tested | Required | Yes |
| Misra2004:17.1 | Pointer arithmetic shall only be applied to pointers that address an array or array element | Required | Yes |
| Misra2004:17.2 | Pointer subtraction shall only be applied to pointers that address elements of the same array | Required | Yes |
| Misra2004:17.3 | , =, <,><= shall="shall" not="not" be="be" applied="applied" to="to" pointer="pointer" types="types" except="except" where="where" they="they" point="point" the="the" same="same" array="array"></=></,> | Required | Yes |
| Misra2004:17.4 | Array indexing shall be the only allowed form of pointer arithmetic | Required | Yes |
| Misra2004:17.5 | The declaration of objects should contain no more than 2 levels of pointer indirection | Advisory | No |
| Misra2004:17.6 | The address of an object with automatic storage shall not be assigned to another object that may persist after the first object has ceased to exist | Required | Yes |
| Misra2004:18.1 | All structure or union types shall be complete at the end of a translation unit | Required | No |
| Misra2004:18.2 | An object shall not be assigned to an overlapping object | Required | Yes |
| Misra2004:18.3 | An area of memory shall not be reused for unrelated purposes | Required | No |
| Misra2004:18.4 | Unions shall not be used | Required | Yes |
| Misra2004:19.1 | #include statements in a file should only be preceded by other preprocessor directives or comments | Advisory | Yes |
| Misra2004:19.2 | Non-standard characters should not occur in header file names in #include directives | Advisory | Yes |
| Misra2004:19.3 | The #include directive shall be followed by either a or "filename" sequence | Required | Yes |
| Misra2004:19.4 | C macros shall only expand to a braced initialiser, a constant, a string literal, a parenthesised expression, a type qualifier, a storage class specifier, or a do-whilezero construct | Required | Yes |
| Misra2004:19.5 | Macros shall not be #define'd or #undef'd within a block | Required | Yes |
| Misra2004:19.6 | #undef shall not be used | Required | Yes |
| Misra2004:19.7 | A function should be used in preference to a function-like macro | Advisory | Yes |
| Misra2004:19.8 | A function-like macro shall not be invoked without all of its arguments | Required | No |
| Misra2004:19.9 | Arguments to a function-like macro shall not contain tokens that look like preprocessing directives | Required | Yes |
| Misra2004:19.10 | In the definition of a function-like macro each instance of a parameter shall be enclosed in parentheses unless it is used as the operand of # or ## | Required | No |
| Misra2004:19.11 | All macro identifiers in preprocessor directives shall be defined before use, except in #ifdef and #ifndef preprocessor directives and the defined() operator | Required | Yes |
| Misra2004:19.12 | There shall be at most one occurrence of the # or ## preprocessor operators in a single macro definition | Required | No |
| Misra2004:19.13 | The # and ## preprocessor operators should not be used | Advisory | Yes |
| Misra2004:19.14 | The defined preprocessor operator shall only be used in one of the two standard forms | Required | No |
| Misra2004:19.15 | Precautions shall be taken in order to prevent the contents of a header file being included twice | Required | No |
| Misra2004:19.16 | Preprocessing directives shall be syntactically meaningful even when excluded by the preprocessor | Required | No |
| Misra2004:19.17 | All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if or #ifdef directive to which they are related | Required | Yes |
| Misra2004:20.1 | Reserved identifiers, macros and functions in the standard library, shall not be defined, redefined or undefined | Required | Yes |
| Misra2004:20.2 | The names of standard library macros, objects and functions shall not be reused | Required | Yes |
| Misra2004:20.3 | The validity of values passed to library functions shall be checked | Required | Yes |
| Misra2004:20.4 | Dynamic heap memory allocation shall not be used | Required | Yes |
| Misra2004:20.5 | The error indicator errno shall not be used | Required | Yes |
| Misra2004:20.6 | The macro offsetof, in library , shall not be used | Required | Yes |
| Misra2004:20.7 | The setjmp macro and the longjmp function shall not be used | Required | Yes |
| Misra2004:20.8 | The signal handling facilities of shall not be used | Required | Yes |
| Misra2004:20.9 | The input/output library shall not be used in production code | Required | Yes |
| Misra2004:20.10 | The library functions atof, atoi and atol from library shall not be used | Required | Yes |
| Misra2004:20.11 | The library functions abort, exit, getenv and system from library shall not be used | Required | Yes |
| Misra2004:20.12 | The time handling functions of library shall not be used | Required | Yes |
| Misra2004:21.1 | Minimisation of run-time failures shall be ensured by the use of at least one of (a) static analysis tools/techniques; (b) dynamic analysis tools/techniques; (c) explicit coding of checks to handle run-time faults | Required | No |
MISRA C++ 2008
Mapping Summary
| Supported | All | Percent Coverage | |
|---|---|---|---|
| All | 167 | 228 | 73.2% |
| Required | 154 | 198 | 77.8% |
| Advisory | 10 | 18 | 55.6% |
| Document | 3 | 12 | 25.0% |
Mapping Detail
| Rule | Rule Name | Category | Supported |
|---|---|---|---|
| MisraC++2008:0-1-1 | A project shall not contain unreachable code. | Required | Yes |
| MisraC++2008:0-1-2 | A project shall not contain infeasible paths. | Required | Yes |
| MisraC++2008:0-1-3 | A project shall not contain unused variables. | Required | Yes |
| MisraC++2008:0-1-4 | A project shall not contain non-volatile POD variables having only one use. | Required | Yes |
| MisraC++2008:0-1-5 | A project shall not contain unused type declarations. | Required | Yes |
| MisraC++2008:0-1-6 | A project shall not contain instances of non-volatile variables being given values that are never subsequently used. | Required | Yes |
| MisraC++2008:0-1-7 | The value returned by a function having a non-void return type that is not an overloaded operator shall always be used. | Required | Yes |
| MisraC++2008:0-1-8 | All functions with void return type shall have external side effect(s). | Required | Yes |
| MisraC++2008:0-1-9 | There shall be no dead code. | Required | Yes |
| MisraC++2008:0-1-10 | Every defined function shall be called at least once. | Required | Yes |
| MisraC++2008:0-1-11 | There shall be no unused parameters (named or unnamed) in non-virtual functions. | Required | Yes |
| MisraC++2008:0-1-12 | There shall be no unused parameters (named or unnamed) in the set of parameters for a virtual function and all the functions that override it. | Required | Yes |
| MisraC++2008:0-2-1 | An object shall not be assigned to an overlapping object. | Required | Yes |
| MisraC++2008:0-3-1 | Minimization of run-time failures shall be ensured by the use of at least one of:(a) static analysis tools/techniques; (b) dynamic analysis tools/techniques; (c) explicit coding of checks to handle run-time faults. | Document | No |
| MisraC++2008:0-3-2 | If a function generates error information, then that error information shall be tested. | Required | Yes |
| MisraC++2008:0-4-1 | Use of scaled-integer or fixed-point arithmetic shall be documented. | Document | No |
| MisraC++2008:0-4-2 | Use of floating-point arithmetic shall be documented. | Document | No |
| MisraC++2008:0-4-3 | Floating-point implementations shall comply with a defined floating-point standard. | Document | No |
| MisraC++2008:1-0-1 | All code shall conform to ISO/IEC 14882:2003 "The C++ Standard Incorporating Technical Corrigendum 1." | Required | No |
| MisraC++2008:1-0-2 | Multiple compilers shall only be used if they have a common, defined interface. | Document | No |
| MisraC++2008:1-0-3 | The implementation of integer division in the chosen compiler shall be determined and documented. | Document | No |
| MisraC++2008:2-2-1 | The character set and the corresponding encoding shall be documented. | Document | No |
| MisraC++2008:2-3-1 | Trigraphs shall not be used. | Required | Yes |
| MisraC++2008:2-5-1 | Digraphs should not be used. | Advisory | No |
| MisraC++2008:2-7-1 | The character sequence /* shall not be used within a C-style comment. | Required | Yes |
| MisraC++2008:2-7-2 | Sections of code shall not be "commented out" using C-style comments. | Required | Yes |
| MisraC++2008:2-7-3 | Sections of code should not be "commented out" using C++ comments. | Advisory | Yes |
| MisraC++2008:2-10-1 | Different identifiers shall be typographically unambiguous. | Required | Yes |
| MisraC++2008:2-10-2 | Identifiers declared in an inner scope shall not hide an identifier declared in an outer scope. | Required | Yes |
| MisraC++2008:2-10-3 | A typedef name (including qualification, if any) shall be a unique identifier. | Required | Yes |
| MisraC++2008:2-10-4 | A class, union or enum name (including qualification, if any) shall be a unique identifier. | Required | Yes |
| MisraC++2008:2-10-5 | The identifier name of a non-member object or function with static storage duration should not be reused. | Advisory | Yes |
| MisraC++2008:2-10-6 | If an identifier refers to a type, it shall not also refer to an object or a function in the same scope. | Required | Yes |
| MisraC++2008:2-13-1 | Only those escape sequences that are defined in ISO/IEC 14882:2003 shall be used. | Required | No |
| MisraC++2008:2-13-2 | Octal constants (other than zero) and octal escape sequences (other than "\0") shall not be used. | Required | Yes |
| MisraC++2008:2-13-3 | A "U" suffix shall be applied to all octal or hexadecimal integer literals of unsigned type. | Required | Yes |
| MisraC++2008:2-13-4 | Literal suffixes shall be upper case. | Required | Yes |
| MisraC++2008:2-13-5 | Narrow and wide string literals shall not be concatenated. | Required | No |
| MisraC++2008:3-1-1 | It shall be possible to include any header file in multiple translation units without violating the One Definition Rule. | Required | Yes |
| MisraC++2008:3-1-2 | Functions shall not be declared at block scope. | Required | Yes |
| MisraC++2008:3-1-3 | When an array is declared, its size shall either be stated explicitly or defined implicitly by initialization. | Required | Yes |
| MisraC++2008:3-2-1 | All declarations of an object or function shall have compatible types. | Required | Yes |
| MisraC++2008:3-2-2 | The One Definition Rule shall not be violated. | Required | Yes |
| MisraC++2008:3-2-3 | A type, object or function that is used in multiple translation units shall be declared in one and only one file. | Required | Yes |
| MisraC++2008:3-2-4 | An identifier with external linkage shall have exactly one definition. | Required | Yes |
| MisraC++2008:3-3-1 | Objects or functions with external linkage shall be declared in a header file. | Required | No |
| MisraC++2008:3-3-2 | If a function has internal linkage then all re-declarations shall include the static storage class specifier. | Required | No |
| MisraC++2008:3-4-1 | An identifier declared to be an object or type shall be defined in a block that minimizes its visibility. | Required | Yes |
| MisraC++2008:3-9-1 | The types used for an object, a function return type, or a function parameter shall be token-for-token identical in all declarations and re-declarations. | Required | Yes |
| MisraC++2008:3-9-2 | typedefs that indicate size and signedness should be used in place of the basic numerical types. | Advisory | Yes |
| MisraC++2008:3-9-3 | The underlying bit representations of floating-point values shall not be used. | Required | Yes |
| MisraC++2008:4-5-1 | Expressions with type bool shall not be used as operands to built-in operators other than the assignment operator = , the logical operators && , || , ! , the equality operators == and != , the unary & operator, and the conditional operator. | Required | Yes |
| MisraC++2008:4-5-2 | Expressions with type enum shall not be used as operands to built-in operators other than the subscript operator [ ] , the assignment operator = , the equality operators == and != , the unary & operator, and the relational operators <,><= ,=","> , = .</=></,> | Required | Yes |
| MisraC++2008:4-5-3 | Expressions with type (plain) char and wchar_t shall not be used as operands to built-in operators other than the assignment operator = , the equality operators == and != , and the unary & operator. | Required | Yes |
| MisraC++2008:4-10-1 | NULL shall not be used as an integer value. | Required | Yes |
| MisraC++2008:4-10-2 | Literal zero (0) shall not be used as the null-pointer-constant. | Required | Yes |
| MisraC++2008:5-0-1 | The value of an expression shall be the same under any order of evaluation that the standard permits. | Required | Yes |
| MisraC++2008:5-0-2 | Limited dependence should be placed on C++ operator precedence rules in expressions. | Advisory | Yes |
| MisraC++2008:5-0-3 | A cvalue expression shall not be implicitly converted to a different underlying type. | Required | Yes |
| MisraC++2008:5-0-4 | An implicit integral conversion shall not change the signedness of the underlying type. | Required | Yes |
| MisraC++2008:5-0-5 | There shall be no implicit floating-integral conversions. | Required | Yes |
| MisraC++2008:5-0-6 | An implicit integral or floating-point conversion shall not reduce the size of the underlying type. | Required | Yes |
| MisraC++2008:5-0-7 | There shall be no explicit floating-integral conversions of a cvalue expression. | Required | Yes |
| MisraC++2008:5-0-8 | An explicit integral or floating-point conversion shall not increase the size of the underlying type of a cvalue expression. | Required | Yes |
| MisraC++2008:5-0-9 | An explicit integral conversion shall not change the signedness of the underlying type of a cvalue expression. | Required | Yes |
| MisraC++2008:5-0-10 | If the bitwise operators ~ and <></> | Required | Yes |
| MisraC++2008:5-0-11 | The plain char type shall only be used for the storage and use of character values. | Required | Yes |
| MisraC++2008:5-0-12 | signed char and unsigned char type shall only be used for the storage and use of numeric values. | Required | Yes |
| MisraC++2008:5-0-13 | The condition of an if-statement and the condition of an iteration-statement shall have type bool. | Required | Yes |
| MisraC++2008:5-0-14 | The first operand of a conditional-operator shall have type bool. | Required | Yes |
| MisraC++2008:5-0-15 | Array indexing shall be the only form of pointer arithmetic. | Required | Yes |
| MisraC++2008:5-0-16 | A pointer operand and any pointer resulting from pointer arithmetic using that operand shall both address elements of the same array. | Required | Yes |
| MisraC++2008:5-0-17 | Subtraction between pointers shall only be applied to pointers that address elements of the same array. | Required | Yes |
| MisraC++2008:5-0-18 | , = , <,><= shall="shall" not="not" be="be" applied="applied" to="to" objects="objects" of="of" pointer="pointer" type,="type," except="except" where="where" they="they" point="point" the="the" same="same" array.="array."></=></,> | Required | Yes |
| MisraC++2008:5-0-19 | The declaration of objects shall contain no more than two levels of pointer indirection. | Required | Yes |
| MisraC++2008:5-0-20 | Non-constant operands to a binary bitwise operator shall have the same underlying type. | Required | Yes |
| MisraC++2008:5-0-21 | Bitwise operators shall only be applied to operands of unsigned underlying type. | Required | Yes |
| MisraC++2008:5-2-1 | Each operand of a logical && or || shall be a postfix-expression. | Required | No |
| MisraC++2008:5-2-2 | A pointer to a virtual base class shall only be cast to a pointer to a derived class by means of dynamic_cast. | Required | Yes |
| MisraC++2008:5-2-3 | Casts from a base class to a derived class should not be performed on polymorphic types. | Advisory | No |
| MisraC++2008:5-2-4 | C-style casts (other than void casts) and functional notation casts (other than explicit constructor calls) shall not be used. | Required | Yes |
| MisraC++2008:5-2-5 | A cast shall not remove any const or volatile qualification from the type of a pointer or reference. | Required | Yes |
| MisraC++2008:5-2-6 | A cast shall not convert a pointer to a function to any other pointer type, including a pointer to function type. | Required | Yes |
| MisraC++2008:5-2-7 | An object with pointer type shall not be converted to an unrelated pointer type, either directly or indirectly. | Required | Yes |
| MisraC++2008:5-2-8 | An object with integer type or pointer to void type shall not be converted to an object with pointer type. | Required | Yes |
| MisraC++2008:5-2-9 | A cast should not convert a pointer type to an integral type. | Advisory | Yes |
| MisraC++2008:5-2-10 | The increment ( ++ ) and decrement ( -- ) operators should not be mixed with other operators in an expression. | Advisory | Yes |
| MisraC++2008:5-2-11 | The comma operator, && operator and the || operator shall not be overloaded. | Required | Yes |
| MisraC++2008:5-2-12 | An identifier with array type passed as a function argument shall not decay to a pointer. | Required | Yes |
| MisraC++2008:5-3-1 | Each operand of the ! operator, the logical && or the logical || operators shall have type bool. | Required | Yes |
| MisraC++2008:5-3-2 | The unary minus operator shall not be applied to an expression whose underlying type is unsigned. | Required | Yes |
| MisraC++2008:5-3-3 | The unary & operator shall not be overloaded. | Required | Yes |
| MisraC++2008:5-3-4 | Evaluation of the operand to the sizeof operator shall not contain side effects. | Required | Yes |
| MisraC++2008:5-8-1 | The right hand operand of a shift operator shall lie between zero and one less than the width in bits of the underlying type of the left hand operand. | Required | Yes |
| MisraC++2008:5-14-1 | The right hand operand of a logical && or || operator shall not contain side effects. | Required | Yes |
| MisraC++2008:5-17-1 | The semantic equivalence between a binary operator and its assignment operator form shall be preserved. | Required | No |
| MisraC++2008:5-18-1 | The comma operator shall not be used. | Required | Yes |
| MisraC++2008:5-19-1 | Evaluation of constant unsigned integer expressions should not lead to wrap-around. | Advisory | No |
| MisraC++2008:6-2-1 | Assignment operators shall not be used in sub-expressions. | Required | Yes |
| MisraC++2008:6-2-2 | Floating-point expressions shall not be directly or indirectly tested for equality or inequality. | Required | Yes |
| MisraC++2008:6-2-3 | Before preprocessing, a null statement shall only occur on a line ny itself; it may be followed by a comment, provided that the first character following the null statement is a white-space character. | Required | No |
| MisraC++2008:6-3-1 | The statement forming the body of a switch, while, do ... while or for statement shall be a compound statement. | Required | Yes |
| MisraC++2008:6-4-1 | An if ( condition ) construct shall be followed by a compound statement. The else keyword shall be followed by either a compound statement, or another if statement. | Required | Yes |
| MisraC++2008:6-4-2 | All if ... else if constructs shall be terminated with an else clause. | Required | Yes |
| MisraC++2008:6-4-3 | A switch statement shall be a well-formed switch statement. | Required | Yes |
| MisraC++2008:6-4-4 | A switch-label shall only be used when the most closely-enclosing compound statement is the body of a switch statement. | Required | Yes |
| MisraC++2008:6-4-5 | An unconditional throw or break statement shall terminate every non-empty switch-clause. | Required | Yes |
| MisraC++2008:6-4-6 | The final clause of a switch statement shall be the default-clause. | Required | Yes |
| MisraC++2008:6-4-7 | The condition of a switch statement shall not have bool type. | Required | Yes |
| MisraC++2008:6-4-8 | Every switch statement shall have at least one case-clause. | Required | Yes |
| MisraC++2008:6-5-1 | A for loop shall contain a single loop-counter which shall not have floating type. | Required | Yes |
| MisraC++2008:6-5-2 | If loop-counter is not modified by -- or ++ , then, within condition, the loop-counter shall only be used as an operand to <= ,=","><,> or = .</,></=> | Required | No |
| MisraC++2008:6-5-3 | The loop-counter shall not be modified within condition or statement. | Required | Yes |
| MisraC++2008:6-5-4 | The loop-counter shall be modified by one of -- , ++ , -=n , or +=n; where n remains constant for the duration of the loop. | Required | Yes |
| MisraC++2008:6-5-5 | A loop-control-variable other than the loop-counter shall not be modified within condition or expression. | Required | Yes |
| MisraC++2008:6-5-6 | A loop-control-variable other than the loop-counter which is modified in statement shall have type bool. | Required | No |
| MisraC++2008:6-6-1 | Any label referenced by a goto statement shall be declared in the same block, or in a block enclosing the goto statement. | Required | Yes |
| MisraC++2008:6-6-2 | The goto statement shall jump to a label declared later in the same function body. | Required | Yes |
| MisraC++2008:6-6-3 | The continue statement shall only be used within a well-formed for loop. | Required | Yes |
| MisraC++2008:6-6-4 | For any iteration statement there shall be no more than one break or goto statement used for loop termination. | Required | Yes |
| MisraC++2008:6-6-5 | A function shall have a single point of exit at the end of the function. | Required | Yes |
| MisraC++2008:7-1-1 | A variable which is not modified shall be const qualified. | Required | Yes |
| MisraC++2008:7-1-2 | A pointer or reference parameter in a function shall be declared as pointer to const or reference to const if the corresponding object is not modified. | Required | Yes |
| MisraC++2008:7-2-1 | An expression with enum underlying type shall only have values corresponding to the enumerators of the enumeration. | Required | Yes |
| MisraC++2008:7-3-1 | The global namespace shall only contain main, namespace declarations and extern "C" declarations. | Required | Yes |
| MisraC++2008:7-3-2 | The identifier main shall not be used for a function other than the global function main. | Required | No |
| MisraC++2008:7-3-3 | There shall be no unnamed namespaces in header files. | Required | Yes |
| MisraC++2008:7-3-4 | using-directives shall not be used. | Required | Yes |
| MisraC++2008:7-3-5 | Multiple declarations for an identifier in the same namespace shall not straddle a using-declaration for that identifier. | Required | Yes |
| MisraC++2008:7-3-6 | using-directives and using-declarations (excluding class scope or function scope using-declarations) shall not be used in header files. | Required | Yes |
| MisraC++2008:7-4-1 | All usage of assembler shall be documented. | Document | Yes |
| MisraC++2008:7-4-2 | Assembler instructions shall only be introduced using the asm declaration. | Required | Yes |
| MisraC++2008:7-4-3 | Assembly language shall be encapsulated and isolated. | Required | Yes |
| MisraC++2008:7-5-1 | A function shall not return a reference or a pointer to an automatic variable (including parameters), defined within the function. | Required | Yes |
| MisraC++2008:7-5-2 | The address of an object with automatic storage shall not be assigned to another object that may persist after the first object has ceased to exist. | Required | Yes |
| MisraC++2008:7-5-3 | A function shall not return a reference or a pointer to a parameter that is passed by reference or const reference. | Required | No |
| MisraC++2008:7-5-4 | Functions should not call themselves, either directly or indirectly. | Advisory | Yes |
| MisraC++2008:8-0-1 | An init-declarator-list or a member-declarator-list shall consist of a single init-declarator or member-declarator respectively. | Required | No |
| MisraC++2008:8-3-1 | Parameters in an overriding virtual function shall either use the same default arguments as the function they override, or else shall not specify any default arguments. | Required | Yes |
| MisraC++2008:8-4-1 | Functions shall not be defined using the ellipsis notation. | Required | Yes |
| MisraC++2008:8-4-2 | The identifiers used for the parameters in a re-declaration of a function shall be identical to those in the declaration. | Required | Yes |
| MisraC++2008:8-4-3 | All exit paths from a function with non-void return type shall have an explicit return statement with an expression. | Required | Yes |
| MisraC++2008:8-4-4 | A function identifier shall either be used to call the function or it shall be preceded by &. | Required | Yes |
| MisraC++2008:8-5-1 | All variables shall have a defined value before they are used. | Required | Yes |
| MisraC++2008:8-5-2 | Braces shall be used to indicate and match the structure in the non-zero initialization of arrays and structures. | Required | Yes |
| MisraC++2008:8-5-3 | In an enumerator list, the = construct shall not be used to explicitly initialize members other than the first, unless all items are explicitly initialized. | Required | Yes |
| MisraC++2008:9-3-1 | const member functions shall not return non-const pointers or references to class-data. | Required | No |
| MisraC++2008:9-3-2 | Member functions shall not return non-const handles to class-data. | Required | No |
| MisraC++2008:9-3-3 | If a member function can be made static then it shall be made static, otherwise if it can be made const then it shall be made const. | Required | Yes |
| MisraC++2008:9-5-1 | Unions shall not be used. | Required | Yes |
| MisraC++2008:9-6-1 | When the absolute partitioning of bits representing a bit-field is required, then the behaviour and packing of bit-fields shall be documented. | Document | Yes |
| MisraC++2008:9-6-2 | Bit-fields shall be either bool type or an explicitly unsigned or signed integral type. | Required | Yes |
| MisraC++2008:9-6-3 | Bit-fields shall not have enum type. | Required | Yes |
| MisraC++2008:9-6-4 | Named bit-fields with signed integer type shall have a length of more than one bit. | Required | Yes |
| MisraC++2008:10-1-1 | Classes should not be derived from virtual bases. | Advisory | Yes |
| MisraC++2008:10-1-2 | A base class shall only be declared virtual if it is used in a diamond hierarchy. | Required | Yes |
| MisraC++2008:10-1-3 | An accessible base class shall not be both virtual and non-virtual in the same hierarchy. | Required | Yes |
| MisraC++2008:10-2-1 | All accessible entity names within a multiple inheritance hierarchy should be unique. | Advisory | No |
| MisraC++2008:10-3-1 | There shall be no more than one definition of each virtual function on each path through the inheritance hierarchy. | Required | No |
| MisraC++2008:10-3-2 | Each overriding virtual function shall be declared with the virtual keyword. | Required | No |
| MisraC++2008:10-3-3 | A virtual function shall only be overridden by a pure virtual function if it is itself declared as pure virtual. | Required | No |
| MisraC++2008:11-0-1 | Member data in non-POD class types shall be private. | Required | No |
| MisraC++2008:12-1-1 | An object's dynamic type shall not be used from the body of its constructor or destructor. | Required | Yes |
| MisraC++2008:12-1-2 | All constructors of a class should explicitly call a constructor for all of its immediate base classes and all virtual base classes. | Advisory | No |
| MisraC++2008:12-1-3 | All constructors that are callable with a single argument of fundamental type shall be declared explicit. | Required | No |
| MisraC++2008:12-8-1 | A copy constructor shall only initialize its base classes and the non- static members of the class of which it is a member. | Required | Yes |
| MisraC++2008:12-8-2 | The copy assignment operator shall be declared protected or private in an abstract class. | Required | Yes |
| MisraC++2008:14-5-1 | A non-member generic function shall only be declared in a namespace that is not an associated namespace. | Required | No |
| MisraC++2008:14-5-2 | A copy constructor shall be declared when there is a template constructor with a single parameter that is a generic parameter. | Required | No |
| MisraC++2008:14-5-3 | A copy assignment operator shall be declared when there is a template assignment operator with a parameter that is a generic parameter. | Required | No |
| MisraC++2008:14-6-1 | In a class template with a dependent base, any name that may be found in that dependent base shall be referred to using a qualified-id or this- | Required | No |
| MisraC++2008:14-6-2 | The function chosen by overload resolution shall resolve to a function declared previously in the translation unit. | Required | No |
| MisraC++2008:14-7-1 | All class templates, function templates, class template member functions and class template static members shall be instantiated at least once. | Required | No |
| MisraC++2008:14-7-2 | For any given template specialization, an explicit instantiation of the template with the template-arguments used in the specialization shall not render the program ill-formed. | Required | No |
| MisraC++2008:14-7-3 | All partial and explicit specializations for a template shall be declared in the same file as the declaration of their primary template. | Required | Yes |
| MisraC++2008:14-8-1 | Overloaded function templates shall not be explicitly specialized. | Required | No |
| MisraC++2008:14-8-2 | The viable function set for a function call should either contain no function specializations, or only contain function specializations. | Advisory | No |
| MisraC++2008:15-0-1 | Exceptions shall only be used for error handling. | Document | No |
| MisraC++2008:15-0-2 | An exception object should not have pointer type. | Advisory | No |
| MisraC++2008:15-0-3 | Control shall not be transferred into a try or catch block using a goto or a switch statement. | Required | No |
| MisraC++2008:15-1-1 | The assignment-expression of a throw statement shall not itself cause an exception to be thrown. | Required | No |
| MisraC++2008:15-1-2 | NULL shall not be thrown explicitly. | Required | Yes |
| MisraC++2008:15-1-3 | An empty throw ( throw; ) shall only be used in the compound-statement of a catch handler. | Required | No |
| MisraC++2008:15-3-1 | Exceptions shall be raised only after start-up and before termination of the program. | Required | No |
| MisraC++2008:15-3-2 | There should be at least one exception handler to catch all otherwise unhandled exceptions. | Advisory | No |
| MisraC++2008:15-3-3 | Handlers of a function-try-block implementation of a class constructor or destructor shall not reference non-static members from this class or its bases. | Required | No |
| MisraC++2008:15-3-4 | Each exception explicitly thrown in the code shall have a handler of a compatible type in all call paths that could lead to that point. | Required | No |
| MisraC++2008:15-3-5 | A class type exception shall always be caught by reference. | Required | Yes |
| MisraC++2008:15-3-6 | Where multiple handlers are provided in a single try-catch statement or function-try-block for a derived class and some or all of its bases, the handlers shall be ordered most-derived to base class. | Required | Yes |
| MisraC++2008:15-3-7 | Where multiple handlers are provided in a single try-catch statement or function-try-block, any ellipsis (catch-all) handler shall occur last. | Required | Yes |
| MisraC++2008:15-4-1 | If a function is declared with an exception-specification, then all declarations of the same function (in other translation units) shall be declared with the same set of type-ids. | Required | No |
| MisraC++2008:15-5-1 | A class destructor shall not exit with an exception. | Required | No |
| MisraC++2008:15-5-2 | Where a function's declaration includes an exception-specification, the function shall only be capable of throwing exceptions of the indicated type(s). | Required | No |
| MisraC++2008:15-5-3 | The terminate() function shall not be called implicitly. | Required | No |
| MisraC++2008:16-0-1 | #include directives in a file shall only be preceded by preprocessor directives or comments. | Required | Yes |
| MisraC++2008:16-0-2 | Macros shall only be #define'd or #undef'd in the global namespace. | Required | No |
| MisraC++2008:16-0-3 | #undef shall not be used. | Required | Yes |
| MisraC++2008:16-0-4 | Function-like macros shall not be defined. | Required | Yes |
| MisraC++2008:16-0-5 | Arguments to a function-like macro shall not contain tokens that look like preprocessing directives. | Required | Yes |
| MisraC++2008:16-0-6 | In the definition of a function-like macro, each instance of a parameter shall be enclosed in parentheses, unless it is used as the operand of # or ## . | Required | Yes |
| MisraC++2008:16-0-7 | Undefined macro identifiers shall not be used in #if or #elif preprocessor directives, except as operands to the defined operator. | Required | Yes |
| MisraC++2008:16-0-8 | If the # token appears as the first token on a line, then it shall be immediately followed by a preprocessing token. | Required | Yes |
| MisraC++2008:16-1-1 | The defined preprocessor operator shall only be used in one of the two standard forms. | Required | No |
| MisraC++2008:16-1-2 | All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if or #ifdef directive to which they are related. | Required | Yes |
| MisraC++2008:16-2-1 | The pre-processor shall only be used for file inclusion and include guards. | Required | No |
| MisraC++2008:16-2-2 | C++ macros shall only be used for include guards, type qualifiers, or storage class specifiers. | Required | No |
| MisraC++2008:16-2-3 | Include guards shall be provided. | Required | No |
| MisraC++2008:16-2-4 | The ', ", /* or // characters shall not occur in a header file name. | Required | Yes |
| MisraC++2008:16-2-5 | The \ character should not occur in a header file name. | Advisory | Yes |
| MisraC++2008:16-2-6 | The #include directive shall be followed by either a or "filename" sequence. | Required | Yes |
| MisraC++2008:16-3-1 | There shall be at most one occurrence of the # or ## operators in a single macro definition. | Required | No |
| MisraC++2008:16-3-2 | The # and ## operators should not be used. | Advisory | Yes |
| MisraC++2008:16-6-1 | All uses of the #pragma directive shall be documented. | Document | Yes |
| MisraC++2008:17-0-1 | Reserved identifiers, macros and functions in the standard library shall not be defined, redefined or undefined. | Required | Yes |
| MisraC++2008:17-0-2 | The names of standard library macros and objects shall not be reused. | Required | Yes |
| MisraC++2008:17-0-3 | The names of standard library functions shall not be overridden. | Required | Yes |
| MisraC++2008:17-0-4 | All library code shall conform to MISRA C++. | Document | No |
| MisraC++2008:17-0-5 | The setjmp macro and the longjmp function shall not be used. | Required | Yes |
| MisraC++2008:18-0-1 | The C library shall not be used. | Required | Yes |
| MisraC++2008:18-0-2 | The library functions atof, atoi and atol from library shall not be used. | Required | Yes |
| MisraC++2008:18-0-3 | The library functions abort, exit, getenv and system from library shall not be used. | Required | Yes |
| MisraC++2008:18-0-4 | The time handling functions of library shall not be used. | Required | Yes |
| MisraC++2008:18-0-5 | The unbounded functions of library shall not be used. | Required | Yes |
| MisraC++2008:18-2-1 | The macro offsetof shall not be used. | Required | Yes |
| MisraC++2008:18-4-1 | Dynamic heap memory allocation shall not be used. | Required | Yes |
| MisraC++2008:18-7-1 | The signal handling facilities of shall not be used. | Required | Yes |
| MisraC++2008:19-3-1 | The error indicator errno shall not be used. | Required | Yes |
| MisraC++2008:27-0-1 | The stream input/output library shall not be used. | Required | Yes |
MISRA 2012
Mapping Summary
| Decidable | Undecidable | Subtotal | Percent Coverage | ||||
|---|---|---|---|---|---|---|---|
| Supported | All | Supported | All | Supported | All | ||
| All | 149 | 149 | 59 | 72 | 208 | 221 | 94.1% |
| Mandatory | 8 | 8 | 13 | 16 | 21 | 24 | 87.5% |
| Required | 103 | 103 | 36 | 44 | 139 | 147 | 94.6% |
| Advisory | 38 | 38 | 10 | 12 | 48 | 50 | 96.0% |
Mapping Detail
| Rule | Rule Name | Category | Decidability | Supported |
|---|---|---|---|---|
| Misra2012:1.1 | The program shall contain no violations of the standard C syntax and constraints, and shall not exceed the implementation's translation limits | Required | Decidable | Yes |
| Misra2012:1.2 | Language extensions should not be used | Advisory | Undecidable | Yes |
| Misra2012:1.3 | There shall be no occurrence of undefined or critical unspecified behaviour | Required | Undecidable | Yes |
| Misra2012:1.4 | Emergent language features shall not be used | Required | Decidable | Yes |
| Misra2012:1.5 | Obsolescent language features shall not be used | Required | Undecidable | Yes |
| Misra2012:2.1 | A project shall not contain unreachable code | Required | Undecidable | Yes |
| Misra2012:2.2 | A project shall not contain dead code | Required | Undecidable | Yes |
| Misra2012:2.3 | A project should not contain unused type declarations | Advisory | Decidable | Yes |
| Misra2012:2.4 | A project should not contain unused tag declarations | Advisory | Decidable | Yes |
| Misra2012:2.5 | A project should not contain unused macro declarations | Advisory | Decidable | Yes |
| Misra2012:2.6 | A function should not contain unused label declarations | Advisory | Decidable | Yes |
| Misra2012:2.7 | A function should not contain unused parameters | Advisory | Decidable | Yes |
| Misra2012:2.8 | A project should not contain unused object definitions | Advisory | Decidable | Yes |
| Misra2012:3.1 | The character sequences /* and // shall not be used within a comment | Required | Decidable | Yes |
| Misra2012:3.2 | Line-splicing shall not be used in // comments | Required | Decidable | Yes |
| Misra2012:4.1 | Octal and hexadecimal escape sequences shall be terminated | Required | Decidable | Yes |
| Misra2012:4.2 | Trigraphs should not be used | Advisory | Decidable | Yes |
| Misra2012:5.1 | External identifiers shall be distinct | Required | Decidable | Yes |
| Misra2012:5.2 | Identifiers declared in the same scope and name space shall be distinct | Required | Decidable | Yes |
| Misra2012:5.3 | An identifier declared in an inner scope shall not hide an identifier declared in an outer scope | Required | Decidable | Yes |
| Misra2012:5.4 | Macro identifiers shall be distinct | Required | Decidable | Yes |
| Misra2012:5.5 | Identifiers shall be distinct from macro names | Required | Decidable | Yes |
| Misra2012:5.6 | A typedef name shall be a unique identifier | Required | Decidable | Yes |
| Misra2012:5.7 | A tag name shall be a unique identifier | Required | Decidable | Yes |
| Misra2012:5.8 | Identifiers that define objects or functions with external linkage shall be unique | Required | Decidable | Yes |
| Misra2012:5.9 | Identifiers that define objects or functions with internal linkage should be unique | Advisory | Decidable | Yes |
| Misra2012:6.1 | Bit-fields shall only be declared with an appropriate type | Required | Decidable | Yes |
| Misra2012:6.2 | Single-bit named bit fields shall not be of a signed type | Required | Decidable | Yes |
| Misra2012:6.3 | A bit field shall not be declared as a member of a union | Required | Decidable | Yes |
| Misra2012:7.1 | Octal constants shall not be used | Required | Decidable | Yes |
| Misra2012:7.2 | A "u" or "U" suffix shall be applied to all integer constants that are represented in an unsigned type | Required | Decidable | Yes |
| Misra2012:7.3 | The lowercase character "l" shall not be used in a literal suffix | Required | Decidable | Yes |
| Misra2012:7.4 | A string literal shall not be assigned to an object unless the object's type is "pointer to const-qualified char" | Required | Decidable | Yes |
| Misra2012:7.5 | The argument of an integer constant macro shall have an appropriate form | Mandatory | Decidable | Yes |
| Misra2012:7.6 | The small integer variants of the minimum-width integer constant macros shall not be used | Required | Decidable | Yes |
| Misra2012:8.1 | Types shall be explicitly specified | Required | Decidable | Yes |
| Misra2012:8.2 | Function types shall be in prototype form with named parameters | Required | Decidable | Yes |
| Misra2012:8.3 | All declarations of an object or function shall use the same names and type qualifiers | Required | Decidable | Yes |
| Misra2012:8.4 | A compatible declaration shall be visible when an object or function with external linkage is defined | Required | Decidable | Yes |
| Misra2012:8.5 | An external object or function shall be declared once in one and only one file | Required | Decidable | Yes |
| Misra2012:8.6 | An identifier with external linkage shall have exactly one external definition | Required | Decidable | Yes |
| Misra2012:8.7 | Functions and objects should not be defined with external linkage if they are referenced in only one translation unit | Advisory | Decidable | Yes |
| Misra2012:8.8 | The static storage class specifier shall be used in all declarations of objects and functions that have internal linkage | Required | Decidable | Yes |
| Misra2012:8.9 | An object should be declared at block scope if its identifier only appears in a single function | Advisory | Decidable | Yes |
| Misra2012:8.10 | An inline function shall be declared with the static storage class | Required | Decidable | Yes |
| Misra2012:8.11 | When an array with external linkage is declared, its size should be explicitly specified | Advisory | Decidable | Yes |
| Misra2012:8.12 | Within an enumerator list, the value of an implicitly-specified enumeration constant shall be unique | Required | Decidable | Yes |
| Misra2012:8.13 | A pointer should point to a const-qualified type whenever possible | Advisory | Undecidable | Yes |
| Misra2012:8.14 | The restrict type qualifier shall not be used | Required | Decidable | Yes |
| Misra2012:8.15 | All declarations of an object with an explicit alignment specification shall specify the same alignment | Required | Decidable | Yes |
| Misra2012:8.16 | The alignment specification of zero should not appear in an object declaration | Advisory | Decidable | Yes |
| Misra2012:8.17 | At most one explicit alignment specifier should appear in an object declaration | Advisory | Decidable | Yes |
| Misra2012:9.1 | The value of an object with automatic storage duration shall not be read before it has been set | Mandatory | Undecidable | Yes |
| Misra2012:9.2 | The initializer for an aggregate or union shall be enclosed in braces | Required | Decidable | Yes |
| Misra2012:9.3 | Arrays shall not be partially initialized | Required | Decidable | Yes |
| Misra2012:9.4 | An element of an object shall not be initialized more than once | Required | Decidable | Yes |
| Misra2012:9.5 | Where designated initializers are used to initialize an array object the size of the array shall be specified explicitly | Required | Decidable | Yes |
| Misra2012:9.6 | An initializer using chained designators shall not contain initializers without designators | Required | Decidable | Yes |
| Misra2012:9.7 | Atomic objects shall be appropriately initialized before being accessed | Mandatory | Undecidable | Yes |
| Misra2012:10.1 | Operands shall not be of an inappropriate essential type | Required | Decidable | Yes |
| Misra2012:10.2 | Expressions of essentially character type shall not be used inappropriately in addition and subtraction operations | Required | Decidable | Yes |
| Misra2012:10.3 | The value of an expression shall not be assigned to an object with a narrower essential type or of a different essential type category | Required | Decidable | Yes |
| Misra2012:10.4 | Both operands of an operator in which the usual arithmetic conversions are performed shall have the same essential type category | Required | Decidable | Yes |
| Misra2012:10.5 | The value of an expression should not be cast to an inappropriate essential type | Advisory | Decidable | Yes |
| Misra2012:10.6 | The value of a composite expression shall not be assigned to an object with wider essential type | Required | Decidable | Yes |
| Misra2012:10.7 | If 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 | Required | Decidable | Yes |
| Misra2012:10.8 | The value of a composite expression shall not be cast to a different essential type category or a wider essential type | Required | Decidable | Yes |
| Misra2012:11.1 | Conversions shall not be performed between a pointer to a function and any other type | Required | Decidable | Yes |
| Misra2012:11.2 | Conversions shall not be performed between a pointer to an incomplete type and any other type | Required | Decidable | Yes |
| Misra2012:11.3 | A conversion shall not be performed between a pointer to object type and a pointer to a different object type | Required | Decidable | Yes |
| Misra2012:11.4 | A conversion should not be performed between a pointer to object and an integer type | Advisory | Decidable | Yes |
| Misra2012:11.5 | A conversion should not be performed from pointer to void into pointer to object | Advisory | Decidable | Yes |
| Misra2012:11.6 | A cast shall not be performed between pointer to void and an arithmetic type | Required | Decidable | Yes |
| Misra2012:11.7 | A cast shall not be performed between pointer to object and a non-integer arithmetic type | Required | Decidable | Yes |
| Misra2012:11.8 | A conversion shall not remove any const, volatile or _Atomic qualification from the type pointed to by a pointer | Required | Decidable | Yes |
| Misra2012:11.9 | The macro NULL shall be the only permitted form of integer null pointer constant | Required | Decidable | Yes |
| Misra2012:11.10 | The _Atomic qualifier shall not be applied to the incomplete type void | Required | Decidable | Yes |
| Misra2012:12.1 | The precedence of operators within expressions should be made explicit | Advisory | Decidable | Yes |
| Misra2012:12.2 | The 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 operand | Required | Undecidable | Yes |
| Misra2012:12.3 | The comma operator should not be used | Advisory | Decidable | Yes |
| Misra2012:12.4 | Evaluation of constant expressions should not lead to unsigned integer wrap-around | Advisory | Decidable | Yes |
| Misra2012:12.5 | The sizeof operator shall not have an operand which is a function parameter declared as "array of type" | Mandatory | Decidable | Yes |
| Misra2012:12.6 | Structure and union members of atomic objects shall not be directly accessed | Required | Decidable | Yes |
| Misra2012:13.1 | Initializer lists shall not contain persistent side effects | Required | Undecidable | Yes |
| Misra2012:13.2 | The 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 | Required | Undecidable | Yes |
| Misra2012:13.3 | A 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 | Advisory | Decidable | Yes |
| Misra2012:13.4 | The result of an assignment operator should not be used | Advisory | Decidable | Yes |
| Misra2012:13.5 | The right hand operand of a logical && or || operator shall not contain persistent side effects | Required | Undecidable | Yes |
| Misra2012:13.6 | The operand of the sizeof operator shall not contain any expression which has potential side effects | Mandatory | Decidable | Yes |
| Misra2012:14.1 | A loop counter shall not have essentially floating type | Required | Undecidable | Yes |
| Misra2012:14.2 | A for loop shall be well-formed | Required | Undecidable | Yes |
| Misra2012:14.3 | Controlling expressions shall not be invariant | Required | Undecidable | Yes |
| Misra2012:14.4 | The controlling expression of an if statement and the controlling expression of an iteration-statement shall have essentially Boolean type | Required | Decidable | Yes |
| Misra2012:15.1 | The goto statement should not be used | Advisory | Decidable | Yes |
| Misra2012:15.2 | The goto statement shall jump to a label declared later in the same function | Required | Decidable | Yes |
| Misra2012:15.3 | Any label referenced by a goto statement shall be declared in the same block, or in any block enclosing the goto statement | Required | Decidable | Yes |
| Misra2012:15.4 | There should be no more than one break or goto statement used to terminate any iteration statement | Advisory | Decidable | Yes |
| Misra2012:15.5 | A function should have a single point of exit at the end | Advisory | Decidable | Yes |
| Misra2012:15.6 | The body of an iteration-statement or a selection-statement shall be a compound-statement | Required | Decidable | Yes |
| Misra2012:15.7 | All if ... else if constructs shall be terminated with an else statement | Required | Decidable | Yes |
| Misra2012:16.1 | All switch statements shall be well-formed | Required | Decidable | Yes |
| Misra2012:16.2 | A switch label shall only be used when the most closely-enclosing compound statement is the body of a switch statement | Required | Decidable | Yes |
| Misra2012:16.3 | An unconditional break statement shall terminate every switch-clause | Required | Decidable | Yes |
| Misra2012:16.4 | Every switch statement shall have a default label | Required | Decidable | Yes |
| Misra2012:16.5 | A default label shall appear as either the first or the last switch label of a switch statement | Required | Decidable | Yes |
| Misra2012:16.6 | Every switch statement shall have at least two switch-clauses | Required | Decidable | Yes |
| Misra2012:16.7 | A switch-expression shall not have essentially Boolean type | Required | Decidable | Yes |
| Misra2012:17.1 | The standard header file shall not be used | Required | Decidable | Yes |
| Misra2012:17.2 | Functions shall not call themselves, either directly or indirectly | Required | Undecidable | Yes |
| Misra2012:17.3 | A function shall not be declared implicitly | Mandatory | Decidable | Yes |
| Misra2012:17.4 | All exit paths from a function with non-void return type shall have an explicit return statement with an expression | Mandatory | Decidable | Yes |
| Misra2012:17.5 | The function argument corresponding to a parameter declared to have an array type shall have an appropriate number of elements | Advisory | Undecidable | Yes |
| Misra2012:17.6 | The declaration of an array parameter shall not contain the static keyword between the [ ] | Mandatory | Decidable | Yes |
| Misra2012:17.7 | The value returned by a function having non-void return type shall be used | Required | Decidable | Yes |
| Misra2012:17.8 | A function parameter should not be modified | Advisory | Undecidable | Yes |
| Misra2012:17.9 | A function declared with a _Noreturn function specifier shall not return to its caller | Mandatory | Undecidable | Yes |
| Misra2012:17.10 | A function declared with a _Noreturn function specifier shall have void return type | Required | Decidable | Yes |
| Misra2012:17.11 | A function that never returns should be declared with a _Noreturn function specifier | Advisory | Undecidable | Yes |
| Misra2012:17.12 | A function identifier should only be used with either a preceding &, or with a parenthesized parameter list | Advisory | Decidable | Yes |
| Misra2012:17.13 | A function type shall not be type qualified | Required | Decidable | Yes |
| Misra2012:18.1 | A pointer resulting from arithmetic on a pointer operand shall address an element of the same array as that pointer operand | Required | Undecidable | Yes |
| Misra2012:18.2 | Subtraction between pointers shall only be applied to pointers that address elements of the same array | Required | Undecidable | Yes |
| Misra2012:18.3 | The relational operators , =, <= shall="shall" not="not" be="be" applied="applied" to="to" expressions="expressions" of="of" pointer="pointer" type="type" except="except" where="where" they="they" point="point" into="into" the="the" same="same" object="object"></=> | Required | Undecidable | Yes |
| Misra2012:18.4 | The +, -, += and -= operators should not be applied to an expression of pointer type | Advisory | Decidable | Yes |
| Misra2012:18.5 | Declarations should contain no more than two levels of pointer nesting | Advisory | Decidable | Yes |
| Misra2012:18.6 | The address of an object with automatic or thread-local storage shall not be copied to another object that persists after the first object has ceased to exist | Required | Undecidable | Yes |
| Misra2012:18.7 | Flexible array members shall not be declared | Required | Decidable | Yes |
| Misra2012:18.8 | Variable-length array types shall not be used | Required | Decidable | Yes |
| Misra2012:18.9 | An object with temporary lifetime shall not undergo array-to-pointer conversion | Required | Decidable | Yes |
| Misra2012:18.10 | Pointers to variably-modified array types shall not be used | Mandatory | Decidable | Yes |
| Misra2012:19.1 | An object shall not be assigned or copied to an overlapping object | Mandatory | Undecidable | Yes |
| Misra2012:19.2 | The union keyword should not be used | Advisory | Decidable | Yes |
| Misra2012:20.1 | #include directives should only be preceded by preprocessor directives or comments | Advisory | Decidable | Yes |
| Misra2012:20.2 | The ', " or \ characters and the /* or // character sequences shall not occur in a header file name | Required | Decidable | Yes |
| Misra2012:20.3 | The #include directive shall be followed by either a or "filename" sequence | Required | Decidable | Yes |
| Misra2012:20.4 | A macro shall not be defined with the same name as a keyword | Required | Decidable | Yes |
| Misra2012:20.5 | #undef should not be used | Advisory | Decidable | Yes |
| Misra2012:20.6 | Tokens that look like a preprocessing directive shall not occur within a macro argument | Required | Decidable | Yes |
| Misra2012:20.7 | Expressions resulting from the expansion of macro parameters shall be enclosed in parentheses | Required | Decidable | Yes |
| Misra2012:20.8 | The controlling expression of a #if or #elif preprocessing directive shall evaluate to 0 or 1 | Required | Decidable | Yes |
| Misra2012:20.9 | All identifiers used in the controlling expression of #if or #elif preprocessing directives shall be #define'd before evaluation | Required | Decidable | Yes |
| Misra2012:20.10 | The # and ## preprocessor operators should not be used | Advisory | Decidable | Yes |
| Misra2012:20.11 | A macro parameter immediately following a # operator shall not immediately be followed by a ## operator | Required | Decidable | Yes |
| Misra2012:20.12 | A 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 operators | Required | Decidable | Yes |
| Misra2012:20.13 | A line whose first token is # shall be a valid preprocessing directive | Required | Decidable | Yes |
| Misra2012:20.14 | All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if, #ifdef or #ifndef directive to which they are related | Required | Decidable | Yes |
| Misra2012:21.1 | #define and #undef shall not be used on a reserved identifier or reserved macro name | Required | Decidable | Yes |
| Misra2012:21.2 | A reserved identifier or macro name shall not be declared | Required | Decidable | Yes |
| Misra2012:21.3 | The memory allocation and deallocation functions of shall not be used | Required | Decidable | Yes |
| Misra2012:21.4 | The standard header file shall not be used | Required | Decidable | Yes |
| Misra2012:21.5 | The standard header file shall not be used | Required | Decidable | Yes |
| Misra2012:21.6 | The Standard Library input/output functions shall not be used | Required | Decidable | Yes |
| Misra2012:21.7 | The atof, atoi, atol and atoll functions of shall not be used | Required | Decidable | Yes |
| Misra2012:21.8 | The Standard Library termination functions of shall not be used | Required | Decidable | Yes |
| Misra2012:21.9 | The library functions bsearch and qsort of shall not be used | Required | Decidable | Yes |
| Misra2012:21.10 | The Standard Library time and date functions shall not be used | Required | Decidable | Yes |
| Misra2012:21.11 | The standard header file should not be used | Advisory | Decidable | Yes |
| Misra2012:21.12 | The standard header file shall not be used | Required | Decidable | Yes |
| Misra2012:21.13 | Any value passed to a function in shall be representable as an unsigned char or be the value EOF | Mandatory | Undecidable | Yes |
| Misra2012:21.14 | The Standard Library function memcmp shall not be used to compare null terminated strings | Required | Undecidable | Yes |
| Misra2012:21.15 | The pointer arguments to the Standard Library functions memcpy, memmove and memcmp shall be pointers to qualified or unqualified versions of compatible types | Required | Decidable | Yes |
| Misra2012:21.16 | The 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 | Required | Decidable | Yes |
| Misra2012:21.17 | Use of the string handling functions from shall not result in accesses beyond the bounds of the objects referenced by their pointer parameters | Mandatory | Undecidable | Yes |
| Misra2012:21.18 | The size_t argument passed to any function in shall have an appropriate value | Mandatory | Undecidable | Yes |
| Misra2012:21.19 | The pointers returned by the Standard Library functions localeconv, getenv, setlocale or, strerror shall only be used as if they have pointer to const-qualified type | Mandatory | Undecidable | Yes |
| Misra2012:21.20 | The pointer returned by the Standard Library functions asctime, ctime, gmtime, localtime, localeconv, setlocale or strerror shall not be used following a subsequent call to the same function | Mandatory | Undecidable | Yes |
| Misra2012:21.21 | The Standard Library function system of shall not be used | Required | Decidable | Yes |
| Misra2012:21.22 | All operand arguments to any type-generic macros declared in shall have an appropriate essential type | Mandatory | Decidable | Yes |
| Misra2012:21.23 | All operand arguments to any multi-argument type-generic macros declared in shall have the same standard type | Required | Decidable | Yes |
| Misra2012:21.24 | The random number generator functions of shall not be used | Required | Decidable | Yes |
| Misra2012:21.25 | All memory synchronization operations shall be executed in sequentially consistent order | Advisory | Decidable | Yes |
| Misra2012:21.26 | The Standard Library function mtx_timedlock() shall only be invoked on mutex objects of appropriate mutex type | Required | Undecidable | No |
| Misra2012:22.1 | All resources obtained dynamically by means of Standard Library functions shall be explicitly released | Required | Undecidable | Yes |
| Misra2012:22.2 | A block of memory shall only be freed if it was allocated by means of a Standard Library function | Mandatory | Undecidable | Yes |
| Misra2012:22.3 | The same file shall not be open for read and write access at the same time on different streams | Required | Undecidable | Yes |
| Misra2012:22.4 | There shall be no attempt to write to a stream which has been opened as read-only | Mandatory | Undecidable | Yes |
| Misra2012:22.5 | A pointer to a FILE object shall not be dereferenced | Mandatory | Undecidable | Yes |
| Misra2012:22.6 | The value of a pointer to a FILE shall not be used after the associated stream has been closed | Mandatory | Undecidable | Yes |
| Misra2012:22.7 | The macro EOF shall only be compared with the unmodified return value from any Standard Library function capable of returning EOF | Required | Undecidable | Yes |
| Misra2012:22.8 | The value of errno shall be set to zero prior to a call to an errno-setting-function | Required | Undecidable | Yes |
| Misra2012:22.9 | The value of errno shall be tested against zero after calling an errno-setting-function | Required | Undecidable | Yes |
| Misra2012:22.10 | The value of errno shall only be tested when the last function to be called was an errno-setting-function | Required | Undecidable | Yes |
| Misra2012:22.11 | A thread that was previously either joined or detached shall not be subsequently joined nor detached | Required | Undecidable | Yes |
| Misra2012:22.12 | Thread objects, thread synchronization objects, and thread-specific storage pointers shall only be accessed by the appropriate Standard Library functions | Mandatory | Undecidable | No |
| Misra2012:22.13 | Thread objects, thread synchronization objects and thread-specific storage pointers shall have appropriate storage duration | Required | Decidable | Yes |
| Misra2012:22.14 | Thread synchronization objects shall be initialized before being accessed | Mandatory | Undecidable | No |
| Misra2012:22.15 | Thread synchronization objects and thread-specific storage pointers shall not be destroyed until after all threads accessing them have terminated | Required | Undecidable | No |
| Misra2012:22.16 | All mutex objects locked by a thread shall be explicitly unlocked by the same thread | Required | Undecidable | Yes |
| Misra2012:22.17 | No thread shall unlock a mutex or call cnd_wait() or cnd_timedwait() for a mutex it has not locked before | Required | Undecidable | Yes |
| Misra2012:22.18 | Non-recursive mutexes shall not be recursively locked | Required | Undecidable | Yes |
| Misra2012:22.19 | A condition variable shall be associated with at most one mutex object | Required | Undecidable | No |
| Misra2012:22.20 | Thread-specific storage pointers shall be created before being accessed | Mandatory | Undecidable | No |
| Misra2012:23.1 | A generic selection should only be expanded from a macro | Advisory | Decidable | Yes |
| Misra2012:23.2 | A generic selection that is not expanded from a macro shall not contain potential side effects in the controlling expression | Required | Decidable | Yes |
| Misra2012:23.3 | A generic selection should contain at least one non-default association | Advisory | Decidable | Yes |
| Misra2012:23.4 | A generic association shall list an appropriate type | Required | Decidable | Yes |
| Misra2012:23.5 | A generic selection should not depend on implicit pointer type conversion | Advisory | Decidable | Yes |
| Misra2012:23.6 | The controlling expression of a generic selection shall have an essential type that matches its standard type | Required | Decidable | Yes |
| Misra2012:23.7 | A generic selection that is expanded from a macro should evaluate its argument only once | Advisory | Decidable | Yes |
| Misra2012:23.8 | A default association shall appear as either the first or the last association of a generic selection | Advisory | Decidable | Yes |
| Misra2012:D.1.1 | Any implementation-defined behaviour on which the output of the program depends shall be documented and understood | Required | Undecidable | No |
| Misra2012:D.2.1 | All source files shall compile without any compilation errors | Required | Undecidable | No |
| Misra2012:D.3.1 | All code shall be traceable to documented requirements | Required | Undecidable | No |
| Misra2012:D.4.1 | Run-time failures shall be minimized | Required | Undecidable | Yes |
| Misra2012:D.4.2 | All usage of assembly language should be documented | Advisory | Undecidable | No |
| Misra2012:D.4.3 | Assembly language shall be encapsulated and isolated | Required | Undecidable | Yes |
| Misra2012:D.4.4 | Sections of code should not be "commented out" | Advisory | Undecidable | Yes |
| Misra2012:D.4.5 | Identifiers in the same name space with overlapping visibility should be typographically unambiguous | Advisory | Undecidable | Yes |
| Misra2012:D.4.6 | typedefs that indicate size and signedness should be used in place of the basic numerical types | Advisory | Undecidable | Yes |
| Misra2012:D.4.7 | If a function returns error information, then that error information shall be tested | Required | Undecidable | Yes |
| Misra2012:D.4.8 | If a pointer to a structure or union is never dereferenced within a translation unit, then the implementation of the object should be hidden | Advisory | Undecidable | No |
| Misra2012:D.4.9 | A function should be used in preference to a function-like macro where they are interchangeable | Advisory | Undecidable | Yes |
| Misra2012:D.4.10 | Precautions shall be taken in order to prevent the contents of a header file being included more than once | Required | Undecidable | No |
| Misra2012:D.4.11 | The validity of values passed to library functions shall be checked | Required | Undecidable | Yes |
| Misra2012:D.4.12 | Dynamic memory allocation shall not be used | Required | Undecidable | Yes |
| Misra2012:D.4.13 | Functions which are designed to provide operations on a resource should be called in an appropriate sequence | Advisory | Undecidable | Yes |
| Misra2012:D.4.14 | The validity of values received from external sources shall be checked | Required | Undecidable | Yes |
| Misra2012:D.4.15 | Evaluation of floating-point expressions shall not lead to the undetected generation of infinities and NaNs | Required | Undecidable | Yes |
| Misra2012:D.5.1 | There shall be no data races between threads | Required | Undecidable | Yes |
| Misra2012:D.5.2 | There shall be no deadlocks between threads | Required | Undecidable | Yes |
| Misra2012:D.5.3 | There shall be no dynamic thread creation | Required | Undecidable | No |
MISRA C 2023
Mapping Summary
| Decidable | Undecidable | Subtotal | Percent Coverage | ||||
|---|---|---|---|---|---|---|---|
| Supported | All | Supported | All | Supported | All | ||
| All | 149 | 149 | 59 | 72 | 208 | 221 | 94.1% |
| Mandatory | 8 | 8 | 13 | 16 | 21 | 24 | 87.5% |
| Required | 103 | 103 | 36 | 44 | 139 | 147 | 94.6% |
| Advisory | 38 | 38 | 10 | 12 | 48 | 50 | 96.0% |
Mapping Detail
| Rule | Rule Name | Category | Decidability | Supported |
|---|---|---|---|---|
| MisraC2023:1.1 | The program shall contain no violations of the standard C syntax and constraints, and shall not exceed the implementation's translation limits | Required | Decidable | Yes |
| MisraC2023:1.2 | Language extensions should not be used | Advisory | Undecidable | Yes |
| MisraC2023:1.3 | There shall be no occurrence of undefined or critical unspecified behaviour | Required | Undecidable | Yes |
| MisraC2023:1.4 | Emergent language features shall not be used | Required | Decidable | Yes |
| MisraC2023:1.5 | Obsolescent language features shall not be used | Required | Undecidable | Yes |
| MisraC2023:2.1 | A project shall not contain unreachable code | Required | Undecidable | Yes |
| MisraC2023:2.2 | A project shall not contain dead code | Required | Undecidable | Yes |
| MisraC2023:2.3 | A project should not contain unused type declarations | Advisory | Decidable | Yes |
| MisraC2023:2.4 | A project should not contain unused tag declarations | Advisory | Decidable | Yes |
| MisraC2023:2.5 | A project should not contain unused macro declarations | Advisory | Decidable | Yes |
| MisraC2023:2.6 | A function should not contain unused label declarations | Advisory | Decidable | Yes |
| MisraC2023:2.7 | A function should not contain unused parameters | Advisory | Decidable | Yes |
| MisraC2023:2.8 | A project should not contain unused object definitions | Advisory | Decidable | Yes |
| MisraC2023:3.1 | The character sequences /* and // shall not be used within a comment | Required | Decidable | Yes |
| MisraC2023:3.2 | Line-splicing shall not be used in // comments | Required | Decidable | Yes |
| MisraC2023:4.1 | Octal and hexadecimal escape sequences shall be terminated | Required | Decidable | Yes |
| MisraC2023:4.2 | Trigraphs should not be used | Advisory | Decidable | Yes |
| MisraC2023:5.1 | External identifiers shall be distinct | Required | Decidable | Yes |
| MisraC2023:5.2 | Identifiers declared in the same scope and name space shall be distinct | Required | Decidable | Yes |
| MisraC2023:5.3 | An identifier declared in an inner scope shall not hide an identifier declared in an outer scope | Required | Decidable | Yes |
| MisraC2023:5.4 | Macro identifiers shall be distinct | Required | Decidable | Yes |
| MisraC2023:5.5 | Identifiers shall be distinct from macro names | Required | Decidable | Yes |
| MisraC2023:5.6 | A typedef name shall be a unique identifier | Required | Decidable | Yes |
| MisraC2023:5.7 | A tag name shall be a unique identifier | Required | Decidable | Yes |
| MisraC2023:5.8 | Identifiers that define objects or functions with external linkage shall be unique | Required | Decidable | Yes |
| MisraC2023:5.9 | Identifiers that define objects or functions with internal linkage should be unique | Advisory | Decidable | Yes |
| MisraC2023:6.1 | Bit-fields shall only be declared with an appropriate type | Required | Decidable | Yes |
| MisraC2023:6.2 | Single-bit named bit fields shall not be of a signed type | Required | Decidable | Yes |
| MisraC2023:6.3 | A bit field shall not be declared as a member of a union | Required | Decidable | Yes |
| MisraC2023:7.1 | Octal constants shall not be used | Required | Decidable | Yes |
| MisraC2023:7.2 | A "u" or "U" suffix shall be applied to all integer constants that are represented in an unsigned type | Required | Decidable | Yes |
| MisraC2023:7.3 | The lowercase character "l" shall not be used in a literal suffix | Required | Decidable | Yes |
| MisraC2023:7.4 | A string literal shall not be assigned to an object unless the object's type is "pointer to const-qualified char" | Required | Decidable | Yes |
| MisraC2023:7.5 | The argument of an integer constant macro shall have an appropriate form | Mandatory | Decidable | Yes |
| MisraC2023:7.6 | The small integer variants of the minimum-width integer constant macros shall not be used | Required | Decidable | Yes |
| MisraC2023:8.1 | Types shall be explicitly specified | Required | Decidable | Yes |
| MisraC2023:8.2 | Function types shall be in prototype form with named parameters | Required | Decidable | Yes |
| MisraC2023:8.3 | All declarations of an object or function shall use the same names and type qualifiers | Required | Decidable | Yes |
| MisraC2023:8.4 | A compatible declaration shall be visible when an object or function with external linkage is defined | Required | Decidable | Yes |
| MisraC2023:8.5 | An external object or function shall be declared once in one and only one file | Required | Decidable | Yes |
| MisraC2023:8.6 | An identifier with external linkage shall have exactly one external definition | Required | Decidable | Yes |
| MisraC2023:8.7 | Functions and objects should not be defined with external linkage if they are referenced in only one translation unit | Advisory | Decidable | Yes |
| MisraC2023:8.8 | The static storage class specifier shall be used in all declarations of objects and functions that have internal linkage | Required | Decidable | Yes |
| MisraC2023:8.9 | An object should be declared at block scope if its identifier only appears in a single function | Advisory | Decidable | Yes |
| MisraC2023:8.10 | An inline function shall be declared with the static storage class | Required | Decidable | Yes |
| MisraC2023:8.11 | When an array with external linkage is declared, its size should be explicitly specified | Advisory | Decidable | Yes |
| MisraC2023:8.12 | Within an enumerator list, the value of an implicitly-specified enumeration constant shall be unique | Required | Decidable | Yes |
| MisraC2023:8.13 | A pointer should point to a const-qualified type whenever possible | Advisory | Undecidable | Yes |
| MisraC2023:8.14 | The restrict type qualifier shall not be used | Required | Decidable | Yes |
| MisraC2023:8.15 | All declarations of an object with an explicit alignment specification shall specify the same alignment | Required | Decidable | Yes |
| MisraC2023:8.16 | The alignment specification of zero should not appear in an object declaration | Advisory | Decidable | Yes |
| MisraC2023:8.17 | At most one explicit alignment specifier should appear in an object declaration | Advisory | Decidable | Yes |
| MisraC2023:9.1 | The value of an object with automatic storage duration shall not be read before it has been set | Mandatory | Undecidable | Yes |
| MisraC2023:9.2 | The initializer for an aggregate or union shall be enclosed in braces | Required | Decidable | Yes |
| MisraC2023:9.3 | Arrays shall not be partially initialized | Required | Decidable | Yes |
| MisraC2023:9.4 | An element of an object shall not be initialized more than once | Required | Decidable | Yes |
| MisraC2023:9.5 | Where designated initializers are used to initialize an array object the size of the array shall be specified explicitly | Required | Decidable | Yes |
| MisraC2023:9.6 | An initializer using chained designators shall not contain initializers without designators | Required | Decidable | Yes |
| MisraC2023:9.7 | Atomic objects shall be appropriately initialized before being accessed | Mandatory | Undecidable | Yes |
| MisraC2023:10.1 | Operands shall not be of an inappropriate essential type | Required | Decidable | Yes |
| MisraC2023:10.2 | Expressions of essentially character type shall not be used inappropriately in addition and subtraction operations | Required | Decidable | Yes |
| MisraC2023:10.3 | The value of an expression shall not be assigned to an object with a narrower essential type or of a different essential type category | Required | Decidable | Yes |
| MisraC2023:10.4 | Both operands of an operator in which the usual arithmetic conversions are performed shall have the same essential type category | Required | Decidable | Yes |
| MisraC2023:10.5 | The value of an expression should not be cast to an inappropriate essential type | Advisory | Decidable | Yes |
| MisraC2023:10.6 | The value of a composite expression shall not be assigned to an object with wider essential type | Required | Decidable | Yes |
| MisraC2023:10.7 | If 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 | Required | Decidable | Yes |
| MisraC2023:10.8 | The value of a composite expression shall not be cast to a different essential type category or a wider essential type | Required | Decidable | Yes |
| MisraC2023:11.1 | Conversions shall not be performed between a pointer to a function and any other type | Required | Decidable | Yes |
| MisraC2023:11.2 | Conversions shall not be performed between a pointer to an incomplete type and any other type | Required | Decidable | Yes |
| MisraC2023:11.3 | A conversion shall not be performed between a pointer to object type and a pointer to a different object type | Required | Decidable | Yes |
| MisraC2023:11.4 | A conversion should not be performed between a pointer to object and an integer type | Advisory | Decidable | Yes |
| MisraC2023:11.5 | A conversion should not be performed from pointer to void into pointer to object | Advisory | Decidable | Yes |
| MisraC2023:11.6 | A cast shall not be performed between pointer to void and an arithmetic type | Required | Decidable | Yes |
| MisraC2023:11.7 | A cast shall not be performed between pointer to object and a non-integer arithmetic type | Required | Decidable | Yes |
| MisraC2023:11.8 | A conversion shall not remove any const, volatile or _Atomic qualification from the type pointed to by a pointer | Required | Decidable | Yes |
| MisraC2023:11.9 | The macro NULL shall be the only permitted form of integer null pointer constant | Required | Decidable | Yes |
| MisraC2023:11.10 | The _Atomic qualifier shall not be applied to the incomplete type void | Required | Decidable | Yes |
| MisraC2023:12.1 | The precedence of operators within expressions should be made explicit | Advisory | Decidable | Yes |
| MisraC2023:12.2 | The 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 operand | Required | Undecidable | Yes |
| MisraC2023:12.3 | The comma operator should not be used | Advisory | Decidable | Yes |
| MisraC2023:12.4 | Evaluation of constant expressions should not lead to unsigned integer wrap-around | Advisory | Decidable | Yes |
| MisraC2023:12.5 | The sizeof operator shall not have an operand which is a function parameter declared as "array of type" | Mandatory | Decidable | Yes |
| MisraC2023:12.6 | Structure and union members of atomic objects shall not be directly accessed | Required | Decidable | Yes |
| MisraC2023:13.1 | Initializer lists shall not contain persistent side effects | Required | Undecidable | Yes |
| MisraC2023:13.2 | The 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 | Required | Undecidable | Yes |
| MisraC2023:13.3 | A 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 | Advisory | Decidable | Yes |
| MisraC2023:13.4 | The result of an assignment operator should not be used | Advisory | Decidable | Yes |
| MisraC2023:13.5 | The right hand operand of a logical && or || operator shall not contain persistent side effects | Required | Undecidable | Yes |
| MisraC2023:13.6 | The operand of the sizeof operator shall not contain any expression which has potential side effects | Mandatory | Decidable | Yes |
| MisraC2023:14.1 | A loop counter shall not have essentially floating type | Required | Undecidable | Yes |
| MisraC2023:14.2 | A for loop shall be well-formed | Required | Undecidable | Yes |
| MisraC2023:14.3 | Controlling expressions shall not be invariant | Required | Undecidable | Yes |
| MisraC2023:14.4 | The controlling expression of an if statement and the controlling expression of an iteration-statement shall have essentially Boolean type | Required | Decidable | Yes |
| MisraC2023:15.1 | The goto statement should not be used | Advisory | Decidable | Yes |
| MisraC2023:15.2 | The goto statement shall jump to a label declared later in the same function | Required | Decidable | Yes |
| MisraC2023:15.3 | Any label referenced by a goto statement shall be declared in the same block, or in any block enclosing the goto statement | Required | Decidable | Yes |
| MisraC2023:15.4 | There should be no more than one break or goto statement used to terminate any iteration statement | Advisory | Decidable | Yes |
| MisraC2023:15.5 | A function should have a single point of exit at the end | Advisory | Decidable | Yes |
| MisraC2023:15.6 | The body of an iteration-statement or a selection-statement shall be a compound-statement | Required | Decidable | Yes |
| MisraC2023:15.7 | All if ... else if constructs shall be terminated with an else statement | Required | Decidable | Yes |
| MisraC2023:16.1 | All switch statements shall be well-formed | Required | Decidable | Yes |
| MisraC2023:16.2 | A switch label shall only be used when the most closely-enclosing compound statement is the body of a switch statement | Required | Decidable | Yes |
| MisraC2023:16.3 | An unconditional break statement shall terminate every switch-clause | Required | Decidable | Yes |
| MisraC2023:16.4 | Every switch statement shall have a default label | Required | Decidable | Yes |
| MisraC2023:16.5 | A default label shall appear as either the first or the last switch label of a switch statement | Required | Decidable | Yes |
| MisraC2023:16.6 | Every switch statement shall have at least two switch-clauses | Required | Decidable | Yes |
| MisraC2023:16.7 | A switch-expression shall not have essentially Boolean type | Required | Decidable | Yes |
| MisraC2023:17.1 | The standard header file shall not be used | Required | Decidable | Yes |
| MisraC2023:17.2 | Functions shall not call themselves, either directly or indirectly | Required | Undecidable | Yes |
| MisraC2023:17.3 | A function shall not be declared implicitly | Mandatory | Decidable | Yes |
| MisraC2023:17.4 | All exit paths from a function with non-void return type shall have an explicit return statement with an expression | Mandatory | Decidable | Yes |
| MisraC2023:17.5 | The function argument corresponding to a parameter declared to have an array type shall have an appropriate number of elements | Advisory | Undecidable | Yes |
| MisraC2023:17.6 | The declaration of an array parameter shall not contain the static keyword between the [ ] | Mandatory | Decidable | Yes |
| MisraC2023:17.7 | The value returned by a function having non-void return type shall be used | Required | Decidable | Yes |
| MisraC2023:17.8 | A function parameter should not be modified | Advisory | Undecidable | Yes |
| MisraC2023:17.9 | A function declared with a _Noreturn function specifier shall not return to its caller | Mandatory | Undecidable | Yes |
| MisraC2023:17.10 | A function declared with a _Noreturn function specifier shall have void return type | Required | Decidable | Yes |
| MisraC2023:17.11 | A function that never returns should be declared with a _Noreturn function specifier | Advisory | Undecidable | Yes |
| MisraC2023:17.12 | A function identifier should only be used with either a preceding &, or with a parenthesized parameter list | Advisory | Decidable | Yes |
| MisraC2023:17.13 | A function type shall not be type qualified | Required | Decidable | Yes |
| MisraC2023:18.1 | A pointer resulting from arithmetic on a pointer operand shall address an element of the same array as that pointer operand | Required | Undecidable | Yes |
| MisraC2023:18.2 | Subtraction between pointers shall only be applied to pointers that address elements of the same array | Required | Undecidable | Yes |
| MisraC2023:18.3 | The relational operators , =, <= shall="shall" not="not" be="be" applied="applied" to="to" expressions="expressions" of="of" pointer="pointer" type="type" except="except" where="where" they="they" point="point" into="into" the="the" same="same" object="object"></=> | Required | Undecidable | Yes |
| MisraC2023:18.4 | The +, -, += and -= operators should not be applied to an expression of pointer type | Advisory | Decidable | Yes |
| MisraC2023:18.5 | Declarations should contain no more than two levels of pointer nesting | Advisory | Decidable | Yes |
| MisraC2023:18.6 | The address of an object with automatic or thread-local storage shall not be copied to another object that persists after the first object has ceased to exist | Required | Undecidable | Yes |
| MisraC2023:18.7 | Flexible array members shall not be declared | Required | Decidable | Yes |
| MisraC2023:18.8 | Variable-length array types shall not be used | Required | Decidable | Yes |
| MisraC2023:18.9 | An object with temporary lifetime shall not undergo array-to-pointer conversion | Required | Decidable | Yes |
| MisraC2023:18.10 | Pointers to variably-modified array types shall not be used | Mandatory | Decidable | Yes |
| MisraC2023:19.1 | An object shall not be assigned or copied to an overlapping object | Mandatory | Undecidable | Yes |
| MisraC2023:19.2 | The union keyword should not be used | Advisory | Decidable | Yes |
| MisraC2023:20.1 | #include directives should only be preceded by preprocessor directives or comments | Advisory | Decidable | Yes |
| MisraC2023:20.2 | The ', " or \ characters and the /* or // character sequences shall not occur in a header file name | Required | Decidable | Yes |
| MisraC2023:20.3 | The #include directive shall be followed by either a or "filename" sequence | Required | Decidable | Yes |
| MisraC2023:20.4 | A macro shall not be defined with the same name as a keyword | Required | Decidable | Yes |
| MisraC2023:20.5 | #undef should not be used | Advisory | Decidable | Yes |
| MisraC2023:20.6 | Tokens that look like a preprocessing directive shall not occur within a macro argument | Required | Decidable | Yes |
| MisraC2023:20.7 | Expressions resulting from the expansion of macro parameters shall be enclosed in parentheses | Required | Decidable | Yes |
| MisraC2023:20.8 | The controlling expression of a #if or #elif preprocessing directive shall evaluate to 0 or 1 | Required | Decidable | Yes |
| MisraC2023:20.9 | All identifiers used in the controlling expression of #if or #elif preprocessing directives shall be #define'd before evaluation | Required | Decidable | Yes |
| MisraC2023:20.10 | The # and ## preprocessor operators should not be used | Advisory | Decidable | Yes |
| MisraC2023:20.11 | A macro parameter immediately following a # operator shall not immediately be followed by a ## operator | Required | Decidable | Yes |
| MisraC2023:20.12 | A 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 operators | Required | Decidable | Yes |
| MisraC2023:20.13 | A line whose first token is # shall be a valid preprocessing directive | Required | Decidable | Yes |
| MisraC2023:20.14 | All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if, #ifdef or #ifndef directive to which they are related | Required | Decidable | Yes |
| MisraC2023:21.1 | #define and #undef shall not be used on a reserved identifier or reserved macro name | Required | Decidable | Yes |
| MisraC2023:21.2 | A reserved identifier or macro name shall not be declared | Required | Decidable | Yes |
| MisraC2023:21.3 | The memory allocation and deallocation functions of shall not be used | Required | Decidable | Yes |
| MisraC2023:21.4 | The standard header file shall not be used | Required | Decidable | Yes |
| MisraC2023:21.5 | The standard header file shall not be used | Required | Decidable | Yes |
| MisraC2023:21.6 | The Standard Library input/output functions shall not be used | Required | Decidable | Yes |
| MisraC2023:21.7 | The atof, atoi, atol and atoll functions of shall not be used | Required | Decidable | Yes |
| MisraC2023:21.8 | The Standard Library termination functions of shall not be used | Required | Decidable | Yes |
| MisraC2023:21.9 | The library functions bsearch and qsort of shall not be used | Required | Decidable | Yes |
| MisraC2023:21.10 | The Standard Library time and date functions shall not be used | Required | Decidable | Yes |
| MisraC2023:21.11 | The standard header file should not be used | Advisory | Decidable | Yes |
| MisraC2023:21.12 | The standard header file shall not be used | Required | Decidable | Yes |
| MisraC2023:21.13 | Any value passed to a function in shall be representable as an unsigned char or be the value EOF | Mandatory | Undecidable | Yes |
| MisraC2023:21.14 | The Standard Library function memcmp shall not be used to compare null terminated strings | Required | Undecidable | Yes |
| MisraC2023:21.15 | The pointer arguments to the Standard Library functions memcpy, memmove and memcmp shall be pointers to qualified or unqualified versions of compatible types | Required | Decidable | Yes |
| MisraC2023:21.16 | The 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 | Required | Decidable | Yes |
| MisraC2023:21.17 | Use of the string handling functions from shall not result in accesses beyond the bounds of the objects referenced by their pointer parameters | Mandatory | Undecidable | Yes |
| MisraC2023:21.18 | The size_t argument passed to any function in shall have an appropriate value | Mandatory | Undecidable | Yes |
| MisraC2023:21.19 | The pointers returned by the Standard Library functions localeconv, getenv, setlocale or, strerror shall only be used as if they have pointer to const-qualified type | Mandatory | Undecidable | Yes |
| MisraC2023:21.20 | The pointer returned by the Standard Library functions asctime, ctime, gmtime, localtime, localeconv, setlocale or strerror shall not be used following a subsequent call to the same function | Mandatory | Undecidable | Yes |
| MisraC2023:21.21 | The Standard Library function system of shall not be used | Required | Decidable | Yes |
| MisraC2023:21.22 | All operand arguments to any type-generic macros declared in shall have an appropriate essential type | Mandatory | Decidable | Yes |
| MisraC2023:21.23 | All operand arguments to any multi-argument type-generic macros declared in shall have the same standard type | Required | Decidable | Yes |
| MisraC2023:21.24 | The random number generator functions of shall not be used | Required | Decidable | Yes |
| MisraC2023:21.25 | All memory synchronization operations shall be executed in sequentially consistent order | Advisory | Decidable | Yes |
| MisraC2023:21.26 | The Standard Library function mtx_timedlock() shall only be invoked on mutex objects of appropriate mutex type | Required | Undecidable | No |
| MisraC2023:22.1 | All resources obtained dynamically by means of Standard Library functions shall be explicitly released | Required | Undecidable | Yes |
| MisraC2023:22.2 | A block of memory shall only be freed if it was allocated by means of a Standard Library function | Mandatory | Undecidable | Yes |
| MisraC2023:22.3 | The same file shall not be open for read and write access at the same time on different streams | Required | Undecidable | Yes |
| MisraC2023:22.4 | There shall be no attempt to write to a stream which has been opened as read-only | Mandatory | Undecidable | Yes |
| MisraC2023:22.5 | A pointer to a FILE object shall not be dereferenced | Mandatory | Undecidable | Yes |
| MisraC2023:22.6 | The value of a pointer to a FILE shall not be used after the associated stream has been closed | Mandatory | Undecidable | Yes |
| MisraC2023:22.7 | The macro EOF shall only be compared with the unmodified return value from any Standard Library function capable of returning EOF | Required | Undecidable | Yes |
| MisraC2023:22.8 | The value of errno shall be set to zero prior to a call to an errno-setting-function | Required | Undecidable | Yes |
| MisraC2023:22.9 | The value of errno shall be tested against zero after calling an errno-setting-function | Required | Undecidable | Yes |
| MisraC2023:22.10 | The value of errno shall only be tested when the last function to be called was an errno-setting-function | Required | Undecidable | Yes |
| MisraC2023:22.11 | A thread that was previously either joined or detached shall not be subsequently joined nor detached | Required | Undecidable | Yes |
| MisraC2023:22.12 | Thread objects, thread synchronization objects, and thread-specific storage pointers shall only be accessed by the appropriate Standard Library functions | Mandatory | Undecidable | No |
| MisraC2023:22.13 | Thread objects, thread synchronization objects and thread-specific storage pointers shall have appropriate storage duration | Required | Decidable | Yes |
| MisraC2023:22.14 | Thread synchronization objects shall be initialized before being accessed | Mandatory | Undecidable | No |
| MisraC2023:22.15 | Thread synchronization objects and thread-specific storage pointers shall not be destroyed until after all threads accessing them have terminated | Required | Undecidable | No |
| MisraC2023:22.16 | All mutex objects locked by a thread shall be explicitly unlocked by the same thread | Required | Undecidable | Yes |
| MisraC2023:22.17 | No thread shall unlock a mutex or call cnd_wait() or cnd_timedwait() for a mutex it has not locked before | Required | Undecidable | Yes |
| MisraC2023:22.18 | Non-recursive mutexes shall not be recursively locked | Required | Undecidable | Yes |
| MisraC2023:22.19 | A condition variable shall be associated with at most one mutex object | Required | Undecidable | No |
| MisraC2023:22.20 | Thread-specific storage pointers shall be created before being accessed | Mandatory | Undecidable | No |
| MisraC2023:23.1 | A generic selection should only be expanded from a macro | Advisory | Decidable | Yes |
| MisraC2023:23.2 | A generic selection that is not expanded from a macro shall not contain potential side effects in the controlling expression | Required | Decidable | Yes |
| MisraC2023:23.3 | A generic selection should contain at least one non-default association | Advisory | Decidable | Yes |
| MisraC2023:23.4 | A generic association shall list an appropriate type | Required | Decidable | Yes |
| MisraC2023:23.5 | A generic selection should not depend on implicit pointer type conversion | Advisory | Decidable | Yes |
| MisraC2023:23.6 | The controlling expression of a generic selection shall have an essential type that matches its standard type | Required | Decidable | Yes |
| MisraC2023:23.7 | A generic selection that is expanded from a macro should evaluate its argument only once | Advisory | Decidable | Yes |
| MisraC2023:23.8 | A default association shall appear as either the first or the last association of a generic selection | Advisory | Decidable | Yes |
| MisraC2023:D.1.1 | Any implementation-defined behaviour on which the output of the program depends shall be documented and understood | Required | Undecidable | No |
| MisraC2023:D.2.1 | All source files shall compile without any compilation errors | Required | Undecidable | No |
| MisraC2023:D.3.1 | All code shall be traceable to documented requirements | Required | Undecidable | No |
| MisraC2023:D.4.1 | Run-time failures shall be minimized | Required | Undecidable | Yes |
| MisraC2023:D.4.2 | All usage of assembly language should be documented | Advisory | Undecidable | No |
| MisraC2023:D.4.3 | Assembly language shall be encapsulated and isolated | Required | Undecidable | Yes |
| MisraC2023:D.4.4 | Sections of code should not be "commented out" | Advisory | Undecidable | Yes |
| MisraC2023:D.4.5 | Identifiers in the same name space with overlapping visibility should be typographically unambiguous | Advisory | Undecidable | Yes |
| MisraC2023:D.4.6 | typedefs that indicate size and signedness should be used in place of the basic numerical types | Advisory | Undecidable | Yes |
| MisraC2023:D.4.7 | If a function returns error information, then that error information shall be tested | Required | Undecidable | Yes |
| MisraC2023:D.4.8 | If a pointer to a structure or union is never dereferenced within a translation unit, then the implementation of the object should be hidden | Advisory | Undecidable | No |
| MisraC2023:D.4.9 | A function should be used in preference to a function-like macro where they are interchangeable | Advisory | Undecidable | Yes |
| MisraC2023:D.4.10 | Precautions shall be taken in order to prevent the contents of a header file being included more than once | Required | Undecidable | No |
| MisraC2023:D.4.11 | The validity of values passed to library functions shall be checked | Required | Undecidable | Yes |
| MisraC2023:D.4.12 | Dynamic memory allocation shall not be used | Required | Undecidable | Yes |
| MisraC2023:D.4.13 | Functions which are designed to provide operations on a resource should be called in an appropriate sequence | Advisory | Undecidable | Yes |
| MisraC2023:D.4.14 | The validity of values received from external sources shall be checked | Required | Undecidable | Yes |
| MisraC2023:D.4.15 | Evaluation of floating-point expressions shall not lead to the undetected generation of infinities and NaNs | Required | Undecidable | Yes |
| MisraC2023:D.5.1 | There shall be no data races between threads | Required | Undecidable | Yes |
| MisraC2023:D.5.2 | There shall be no deadlocks between threads | Required | Undecidable | Yes |
| MisraC2023:D.5.3 | There shall be no dynamic thread creation | Required | Undecidable | No |
MISRA C++ 2023
Mapping Summary
| Decidable | Undecidable | Subtotal | Percent Coverage | ||||
|---|---|---|---|---|---|---|---|
| Supported | All | Supported | All | Supported | All | ||
| All | 104 | 155 | 20 | 24 | 124 | 179 | 69.3% |
| Mandatory | 2 | 2 | 3 | 3 | 5 | 5 | 100.0% |
| Required | 73 | 110 | 11 | 14 | 84 | 124 | 67.7% |
| Advisory | 29 | 43 | 6 | 7 | 35 | 50 | 70.0% |
Mapping Detail
| Rule | Rule Name | Category | Decidability | Supported |
|---|---|---|---|---|
| MisraC++2023:0.0.1 | A function shall not contain unreachable statements | Required | Decidable | Yes |
| MisraC++2023:0.0.2 | Controlling expressions should not be invariant | Advisory | Undecidable | Yes |
| MisraC++2023:0.1.1 | A value should not be unnecessarily written to a local object | Advisory | Undecidable | Yes |
| MisraC++2023:0.1.2 | The value returned by a function shall be used | Required | Decidable | Yes |
| MisraC++2023:0.2.1 | Variables with limited visibility should be used at least once | Advisory | Decidable | Yes |
| MisraC++2023:0.2.2 | Any named function parameter shall be used at least once | Required | Decidable | Yes |
| MisraC++2023:0.2.3 | Types with limited visibility should be used at least once | Advisory | Decidable | Yes |
| MisraC++2023:0.2.4 | Functions with limited visibility should be used at least once | Advisory | Decidable | No |
| MisraC++2023:0.3.1 | Floating-point arithmetic should be used appropriately | Advisory | Undecidable | Yes |
| MisraC++2023:0.3.2 | A function call shall not violate the function's preconditions | Required | Undecidable | No |
| MisraC++2023:4.1.1 | A program shall conform to ISO/IEC 14882:2017 (C++17) | Required | Undecidable | Yes |
| MisraC++2023:4.1.2 | Deprecated features should not be used | Advisory | Decidable | Yes |
| MisraC++2023:4.1.3 | There shall be no occurrence of undefined or critical unspecified behaviour | Required | Undecidable | Yes |
| MisraC++2023:4.6.1 | Operations on a memory location shall be sequenced appropriately | Required | Undecidable | Yes |
| MisraC++2023:5.0.1 | Trigraph-like sequences should not be used | Advisory | Decidable | Yes |
| MisraC++2023:5.7.1 | The character sequence /* shall not be used within a C-style comment | Required | Decidable | Yes |
| MisraC++2023:5.7.2 | Sections of code should not be "commented out" | Advisory | Undecidable | Yes |
| MisraC++2023:5.7.3 | Line-splicing shall not be used in // comments | Required | Decidable | Yes |
| MisraC++2023:5.10.1 | User-defined identifiers shall have an appropriate form | Required | Decidable | No |
| MisraC++2023:5.13.1 | Within character literals and non raw-string literals, \ shall only be used to form a defined escape sequence or universal character name | Required | Decidable | No |
| MisraC++2023:5.13.2 | Octal and hexadecimal escape sequences shall be terminated | Required | Decidable | Yes |
| MisraC++2023:5.13.3 | Octal constants shall not be used | Required | Decidable | Yes |
| MisraC++2023:5.13.4 | Unsigned integer literals shall be appropriately suffixed | Required | Decidable | Yes |
| MisraC++2023:5.13.5 | The lowercase form of "L" shall not be used as the first character in a literal suffix | Required | Decidable | Yes |
| MisraC++2023:5.13.6 | An integer literal of type long long shall not use a single L or l in any suffix | Required | Decidable | No |
| MisraC++2023:5.13.7 | Strings with different encoding prefixes shall not be concatenated | Required | Decidable | No |
| MisraC++2023:6.0.1 | Block scope declarations shall not be visually ambiguous | Required | Decidable | Yes |
| MisraC++2023:6.0.2 | When an array with external linkage is declared, its size should be explicitly specified | Advisory | Decidable | Yes |
| MisraC++2023:6.0.3 | The only declarations in the global namespace shall be main, namespace declarations and extern "C" declarations | Advisory | Decidable | Yes |
| MisraC++2023:6.0.4 | The identifier main shall not be used for a function other than the global function main | Required | Decidable | No |
| MisraC++2023:6.2.1 | The one-definition rule shall not be violated | Required | Decidable | Yes |
| MisraC++2023:6.2.2 | All declarations of a variable or function shall have the same type | Required | Decidable | Yes |
| MisraC++2023:6.2.3 | The source code used to implement an entity shall appear only once | Required | Decidable | Yes |
| MisraC++2023:6.2.4 | A header file shall not contain definitions of functions or objects that are non-inline and have external linkage | Required | Decidable | Yes |
| MisraC++2023:6.4.1 | A variable declared in an inner scope shall not hide a variable declared in an outer scope | Required | Decidable | Yes |
| MisraC++2023:6.4.2 | Derived classes shall not conceal functions that are inherited from their bases | Required | Decidable | Yes |
| MisraC++2023:6.4.3 | A name that is present in a dependent base shall not be resolved by unqualified lookup | Required | Decidable | No |
| MisraC++2023:6.5.1 | A function or object with external linkage should be introduced in a header file | Advisory | Decidable | No |
| MisraC++2023:6.5.2 | Internal linkage should be specified appropriately | Advisory | Decidable | No |
| MisraC++2023:6.7.1 | Local variables shall not have static storage duration | Required | Decidable | No |
| MisraC++2023:6.7.2 | Global variables shall not be used | Required | Decidable | No |
| MisraC++2023:6.8.1 | An object shall not be accessed outside of its lifetime | Required | Undecidable | Yes |
| MisraC++2023:6.8.2 | A function must not return a reference or a pointer to a local variable with automatic storage duration | Mandatory | Decidable | Yes |
| MisraC++2023:6.8.3 | An assignment operator shall not assign the address of an object with automatic storage duration to an object with a greater lifetime | Required | Decidable | Yes |
| MisraC++2023:6.8.4 | Member functions returning references to their object should be ref-qualified appropriately | Advisory | Decidable | No |
| MisraC++2023:6.9.1 | The same type aliases shall be used in all declarations and re- declarations of the same entity | Required | Decidable | Yes |
| MisraC++2023:6.9.2 | The names of the standard signed integer types and standard unsigned integer types should not be used | Advisory | Decidable | Yes |
| MisraC++2023:7.0.1 | There shall be no conversion from type bool | Required | Decidable | No |
| MisraC++2023:7.0.2 | There shall be no conversion to type bool | Required | Decidable | No |
| MisraC++2023:7.0.3 | The numerical value of a character shall not be used | Required | Decidable | Yes |
| MisraC++2023:7.0.4 | The operands of bitwise operators and shift operators shall be appropriate | Required | Decidable | Yes |
| MisraC++2023:7.0.5 | Integral promotion and the usual arithmetic conversions shall not change the signedness or the type category of an operand | Required | Decidable | Yes |
| MisraC++2023:7.0.6 | Assignment between numeric types shall be appropriate | Required | Decidable | Yes |
| MisraC++2023:7.11.1 | nullptr shall be the only form of the null-pointer-constant | Required | Decidable | Yes |
| MisraC++2023:7.11.2 | An array passed as a function argument shall not decay to a pointer | Required | Decidable | Yes |
| MisraC++2023:7.11.3 | A conversion from function type to pointer-to-function type shall only occur in appropriate contexts | Required | Decidable | Yes |
| MisraC++2023:8.0.1 | Parentheses should be used to make the meaning of an expression appropriately explicit | Advisory | Decidable | Yes |
| MisraC++2023:8.1.1 | A non-transient lambda shall not implicitly capture this | Required | Decidable | No |
| MisraC++2023:8.1.2 | Variables should be captured explicitly in a non-transient lambda | Advisory | Decidable | Yes |
| MisraC++2023:8.2.1 | A virtual base class shall only be cast to a derived class by means of dynamic_cast | Required | Decidable | Yes |
| MisraC++2023:8.2.2 | C-style casts and functional notation casts shall not be used | Required | Decidable | Yes |
| MisraC++2023:8.2.3 | A cast shall not remove any const or volatile qualification from the type accessed via a pointer or by reference | Required | Decidable | Yes |
| MisraC++2023:8.2.4 | Casts shall not be performed between a pointer to a function and any other type | Required | Decidable | Yes |
| MisraC++2023:8.2.5 | reinterpret_cast shall not be used | Required | Decidable | Yes |
| MisraC++2023:8.2.6 | An object with integral, enumerated, or pointer to void type shall not be converted to an object with pointer type | Required | Decidable | Yes |
| MisraC++2023:8.2.7 | A cast should not convert a pointer type to an integral type | Advisory | Decidable | Yes |
| MisraC++2023:8.2.8 | A pointer shall not be cast to an integral type other than std::uintptr_t or std::intptr_t | Required | Decidable | No |
| MisraC++2023:8.2.9 | The operand to typeid shall not be an expression of polymorphic class type | Required | Decidable | No |
| MisraC++2023:8.2.10 | Functions shall not call themselves, either directly or indirectly | Required | Undecidable | Yes |
| MisraC++2023:8.2.11 | An argument passed via ellipsis shall have an appropriate type | Required | Decidable | Yes |
| MisraC++2023:8.3.1 | The built-in unary - operator should not be applied to an expression of unsigned type | Advisory | Decidable | Yes |
| MisraC++2023:8.3.2 | The built-in unary + operator should not be used | Advisory | Decidable | No |
| MisraC++2023:8.7.1 | Pointer arithmetic shall not form an invalid pointer | Required | Undecidable | Yes |
| MisraC++2023:8.7.2 | Subtraction between pointers shall only be applied to pointers that address elements of the same array | Required | Undecidable | Yes |
| MisraC++2023:8.9.1 | The built-in relational operators , =, <= shall="shall" not="not" be="be" applied="applied" to="to" objects="objects" of="of" pointer="pointer" type,="type," except="except" where="where" they="they" point="point" elements="elements" the="the" same="same" array="array"></=> | Required | Undecidable | Yes |
| MisraC++2023:8.14.1 | The right hand operand of a logical && or || operator shall not contain persistent side effects | Advisory | Undecidable | Yes |
| MisraC++2023:8.18.1 | An object or sub-object must not be copied to an overlapping object | Mandatory | Undecidable | Yes |
| MisraC++2023:8.18.2 | The result of an assignment operator should not be used | Advisory | Decidable | Yes |
| MisraC++2023:8.19.1 | The comma operator should not be used | Advisory | Decidable | Yes |
| MisraC++2023:8.20.1 | An unsigned arithmetic operation with constant operands should not wrap | Advisory | Decidable | Yes |
| MisraC++2023:9.2.1 | An explicit type conversion shall not be an expression statement | Required | Decidable | No |
| MisraC++2023:9.3.1 | The body of an iteration-statement or a selection-statement shall be a compound-statement | Required | Decidable | Yes |
| MisraC++2023:9.4.1 | All if ... else if constructs shall be terminated with an else statement | Required | Decidable | Yes |
| MisraC++2023:9.4.2 | The structure of a switch statement shall be appropriate | Required | Decidable | Yes |
| MisraC++2023:9.5.1 | Legacy for statements should be simple | Advisory | Decidable | Yes |
| MisraC++2023:9.5.2 | A for-range-initializer shall contain at most one function call | Required | Decidable | No |
| MisraC++2023:9.6.1 | The goto statement should not be used | Advisory | Decidable | Yes |
| MisraC++2023:9.6.2 | A goto statement shall reference a label in a surrounding block | Required | Decidable | Yes |
| MisraC++2023:9.6.3 | The goto statement shall jump to a label declared later in the function body | Required | Decidable | Yes |
| MisraC++2023:9.6.4 | A function declared with the [[noreturn]] attribute shall not return | Required | Undecidable | Yes |
| MisraC++2023:9.6.5 | A function with non-void return type shall return a value on all paths | Required | Decidable | Yes |
| MisraC++2023:10.0.1 | A declaration shall not declare more than one variable or member variable | Advisory | Decidable | Yes |
| MisraC++2023:10.1.1 | The target type of a pointer or lvalue reference parameter should be const-qualified appropriately | Advisory | Decidable | Yes |
| MisraC++2023:10.1.2 | Volatile qualification shall be used appropriately | Required | Decidable | Yes |
| MisraC++2023:10.2.1 | An enumeration shall be defined with an explicit underlying type | Required | Decidable | No |
| MisraC++2023:10.2.2 | Unscoped enumerations should not be declared | Advisory | Decidable | No |
| MisraC++2023:10.2.3 | The numeric value of an unscoped enumeration with no fixed underlying type shall not be used | Required | Decidable | No |
| MisraC++2023:10.3.1 | There shall be no unnamed namespaces in header files | Advisory | Decidable | Yes |
| MisraC++2023:10.4.1 | The asm declaration shall not be used | Required | Decidable | Yes |
| MisraC++2023:11.3.1 | Variables of array type should not be declared | Advisory | Decidable | No |
| MisraC++2023:11.3.2 | The declaration of objects should contain no more than two levels of pointer indirection | Advisory | Decidable | Yes |
| MisraC++2023:11.6.1 | All variables should be initialized | Advisory | Decidable | Yes |
| MisraC++2023:11.6.2 | The value of an object shall not be read before it has been set | Mandatory | Undecidable | Yes |
| MisraC++2023:11.6.3 | Within an enumerator list, the value of an implicitly-specified enumeration constant shall be unique | Required | Decidable | Yes |
| MisraC++2023:12.2.1 | Bit fields should not be declared | Advisory | Decidable | Yes |
| MisraC++2023:12.2.2 | A bit-field shall have an appropriate type | Required | Decidable | Yes |
| MisraC++2023:12.2.3 | A named bit-field with signed integer type shall not have a length of one bit | Required | Decidable | Yes |
| MisraC++2023:12.3.1 | The union keyword shall not be used | Required | Decidable | Yes |
| MisraC++2023:13.1.1 | Classes should not be inherited virtually | Advisory | Decidable | Yes |
| MisraC++2023:13.1.2 | An accessible base class shall not be both virtual and non-virtual in the same hierarchy | Required | Decidable | Yes |
| MisraC++2023:13.3.1 | User-declared member functions shall use the virtual, override and final specifiers appropriately | Required | Decidable | Yes |
| MisraC++2023:13.3.2 | Parameters in an overriding virtual function shall not introduce different default arguments | Required | Decidable | Yes |
| MisraC++2023:13.3.3 | The parameters in all declarations or overrides of a function shall either be unnamed or have identical names | Required | Decidable | Yes |
| MisraC++2023:13.3.4 | A comparison of a potentially virtual pointer to member shall only be with nullptr | Required | Decidable | Yes |
| MisraC++2023:14.1.1 | Non-static data members should be either all private or all public | Advisory | Decidable | No |
| MisraC++2023:15.0.1 | Special member functions shall be provided appropriately | Required | Decidable | No |
| MisraC++2023:15.0.2 | User-provided copy and move member functions of a class should have appropriate signatures | Advisory | Decidable | Yes |
| MisraC++2023:15.1.1 | An object's dynamic type shall not be used from within its constructor or destructor | Required | Undecidable | Yes |
| MisraC++2023:15.1.2 | All constructors of a class should explicitly initialize all of its immediate base classes and virtual base classes | Advisory | Decidable | No |
| MisraC++2023:15.1.3 | Conversion operators and constructors that are callable with a single argument shall be explicit | Required | Decidable | No |
| MisraC++2023:15.1.4 | All direct non-static data members of a class should be initialized before the class object is accessible | Advisory | Decidable | No |
| MisraC++2023:15.1.5 | A class shall only define an initializer-list constructor when it is the only constructor | Required | Decidable | No |
| MisraC++2023:15.8.1 | User-provided copy assignment and move assignment operators shall handle self-assignment | Required | Undecidable | No |
| MisraC++2023:16.5.1 | The logical AND and logical OR operators shall not be overloaded | Required | Decidable | Yes |
| MisraC++2023:16.5.2 | The address-of operator shall not be overloaded | Required | Decidable | Yes |
| MisraC++2023:16.6.1 | Symmetrical operators should only be implemented as non-member functions | Advisory | Decidable | No |
| MisraC++2023:17.8.1 | Function templates shall not be explicitly specialized | Required | Decidable | No |
| MisraC++2023:18.1.1 | An exception object shall not have pointer type | Required | Decidable | No |
| MisraC++2023:18.1.2 | An empty throw shall only occur within the compound-statement of a catch handler | Required | Decidable | Yes |
| MisraC++2023:18.3.1 | There should be at least one exception handler to catch all otherwise unhandled exceptions | Advisory | Decidable | No |
| MisraC++2023:18.3.2 | An exception of class type shall be caught by const reference or reference | Required | Decidable | Yes |
| MisraC++2023:18.3.3 | Handlers for a function-try-block of a constructor or destructor shall not refer to non-static members from their class or its bases | Required | Decidable | No |
| MisraC++2023:18.4.1 | Exception-unfriendly functions shall be noexcept | Required | Decidable | No |
| MisraC++2023:18.5.1 | A noexcept function should not attempt to propagate an exception to the calling function | Advisory | Undecidable | No |
| MisraC++2023:18.5.2 | Program-terminating functions should not be used | Advisory | Decidable | Yes |
| MisraC++2023:19.0.1 | A line whose first token is # shall be a valid preprocessing directive | Required | Decidable | Yes |
| MisraC++2023:19.0.2 | Function-like macros shall not be defined | Required | Decidable | Yes |
| MisraC++2023:19.0.3 | #include directives should only be preceded by preprocessor directives or comments | Advisory | Decidable | Yes |
| MisraC++2023:19.0.4 | #undef should only be used for macros defined previously in the same file | Advisory | Decidable | Yes |
| MisraC++2023:19.1.1 | The defined preprocessor operator shall be used appropriately | Required | Decidable | No |
| MisraC++2023:19.1.2 | All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if, #ifdef or #ifndef directive to which they are related | Required | Decidable | Yes |
| MisraC++2023:19.1.3 | All identifiers used in the controlling expression of #if or #elif preprocessing directives shall be #define'd at the point of evaluation | Required | Decidable | Yes |
| MisraC++2023:19.2.1 | Precautions shall be taken in order to prevent the contents of a header file being included more than once | Required | Decidable | No |
| MisraC++2023:19.2.2 | The #include directive shall be followed by either a or "filename" sequence | Required | Decidable | Yes |
| MisraC++2023:19.2.3 | The ', \ or " characters and the /* or // character sequences shall not occur in a header file name | Required | Decidable | Yes |
| MisraC++2023:19.3.1 | The # and ## preprocessor operators should not be used | Advisory | Decidable | Yes |
| MisraC++2023:19.3.2 | A macro parameter immediately following a # operator shall not immediately be followed by a ## operator | Required | Decidable | Yes |
| MisraC++2023:19.3.3 | The argument to a mixed-use macro parameter shall not be subject to further expansion | Required | Decidable | No |
| MisraC++2023:19.3.4 | Parentheses shall be used to ensure macro arguments are expanded appropriately | Required | Decidable | Yes |
| MisraC++2023:19.3.5 | Tokens that look like a preprocessing directive shall not occur within a macro argument | Required | Decidable | Yes |
| MisraC++2023:19.6.1 | The #pragma directive and the _Pragma operator should not be used | Advisory | Decidable | Yes |
| MisraC++2023:21.2.1 | The library functions atof, atoi, atol and atoll from shall not be used | Required | Decidable | Yes |
| MisraC++2023:21.2.2 | The string handling functions from , , and shall not be used | Required | Decidable | Yes |
| MisraC++2023:21.2.3 | The Standard Library function system of shall not be used | Required | Decidable | Yes |
| MisraC++2023:21.2.4 | The macro offsetof shall not be used | Required | Decidable | Yes |
| MisraC++2023:21.6.1 | Dynamic memory shall not be used | Advisory | Undecidable | Yes |
| MisraC++2023:21.6.2 | Dynamic memory shall be managed automatically | Required | Decidable | Yes |
| MisraC++2023:21.6.3 | Advanced memory management shall not be used | Required | Decidable | No |
| MisraC++2023:21.6.4 | If a project defines either a sized or unsized version of a global delete operator, then both shall be defined | Required | Decidable | No |
| MisraC++2023:21.6.5 | A pointer to an incomplete class type shall not be deleted | Required | Decidable | No |
| MisraC++2023:21.10.1 | The features of shall not be used | Required | Decidable | Yes |
| MisraC++2023:21.10.2 | The standard header file shall not be used | Required | Decidable | Yes |
| MisraC++2023:21.10.3 | The facilities provided by the standard header file shall not be used | Required | Decidable | Yes |
| MisraC++2023:22.3.1 | The assert macro shall not be used with a constant-expression | Required | Decidable | No |
| MisraC++2023:22.4.1 | The literal value zero shall be the only value assigned to errno | Required | Decidable | No |
| MisraC++2023:23.11.1 | The raw pointer constructors of std::shared_ptr and std::unique_ptr should not be used | Advisory | Decidable | No |
| MisraC++2023:24.5.1 | The character handling functions from and shall not be used | Required | Decidable | No |
| MisraC++2023:24.5.2 | The C++ Standard Library functions memcpy, memmove and memcmp from shall not be used | Required | Decidable | Yes |
| MisraC++2023:25.5.1 | The setlocale and std::locale::global functions shall not be called | Required | Decidable | Yes |
| MisraC++2023:25.5.2 | The pointers returned by the Standard Library functions localeconv, getenv, setlocale or, strerror must only be used as if they have pointer to const-qualified type | Mandatory | Decidable | Yes |
| MisraC++2023:25.5.3 | The pointer returned by the C Standard Library functions asctime, ctime, gmtime, localtime, localeconv, getenv, setlocale or strerror must not be used following a subsequent call to the same function | Mandatory | Undecidable | Yes |
| MisraC++2023:26.3.1 | std::vector should not be specialized with bool | Advisory | Decidable | No |
| MisraC++2023:28.3.1 | Predicates shall not have persistent side effects | Required | Undecidable | No |
| MisraC++2023:28.6.1 | The argument to std::move shall be a non-const lvalue | Required | Decidable | No |
| MisraC++2023:28.6.2 | Forwarding references and std::forward shall be used together | Required | Decidable | No |
| MisraC++2023:28.6.3 | An object shall not be used while in a potentially moved-from state | Required | Decidable | No |
| MisraC++2023:28.6.4 | The result of std::remove, std::remove_if, std::unique and empty shall be used | Required | Decidable | No |
| MisraC++2023:30.0.1 | The C Library input/output functions shall not be used | Required | Decidable | Yes |
| MisraC++2023:30.0.2 | Reads and writes on the same file stream shall be separated by a positioning operation | Required | Undecidable | Yes |