MISRA C:2023 Directives and Rules

List and description of MISRA™ C:2023 directives and rules that are supported by Polyspace^®

Polyspace can check your code against the MISRA C™:2023 coding rules and directives. The MISRA C:2023 standard consolidates these guidelines:

MISRA C:2012 rules and directives.
Clarifications added in technical corrigendum 1 (TC1) and technical corrigendum 2 (TC2).
New rules and modifications added in amendment 1 (AMD1), amendment 2 (AMD2), amendment 3 (AMD3), and amendment 4 (AMD4).

Each guideline is categorized into one of these categories: mandatory, required, or advisory. When you set up rule checking, you can select subsets of these categories to check. Use the analysis option Check MISRA C:2023 (-misra-c-2023) to activate subsets of the rules.

For automatically generated code, some rules change categories, including to one additional category: readability. The option Use generated code requirements (-misra-c-2023-agc-mode) activates the categorization for automatically generated code.

There are additional subsets of MISRA C:2023 guidelines defined by Polyspace called Software Quality Objectives (SQO) that can have a direct or indirect impact on the precision of your results. When you set up code checking, you can select these subsets. See Software Quality Objective Subsets for MISRA Coding Standards

If you use a specific version of the C language such as C11 or C17/C18, specify the C version for a more accurate check for MISRA C:2023 violation. See C standard version (-c-version).

Polyspace Results

expand all

Directives — Implementation

MISRA C:2023 Dir 1.1 Any implementation-defined behavior on which the output of the program depends shall be documented and understood (Since R2024a)

Directives — Compilation and Build

MISRA C:2023 Dir 2.1 All source files shall compile without any compilation errors (Since R2024a)

Directives — Code Design

`MISRA C:2023 Dir 4.1`	Run-time failures shall be minimized (Since R2024a)
`MISRA C:2023 Dir 4.3`	Assembly language shall be encapsulated and isolated (Since R2024a)
`MISRA C:2023 Dir 4.4`	Sections of code should not be "commented out" (Since R2024a)
`MISRA C:2023 Dir 4.5`	Identifiers in the same name space with overlapping visibility should be typographically unambiguous (Since R2024a)
`MISRA C:2023 Dir 4.6`	`typedefs` that indicate size and signedness should be used in place of the basic numerical types (Since R2024a)
`MISRA C:2023 Dir 4.7`	If a function returns error information, then that error information shall be tested (Since R2024a)
`MISRA C:2023 Dir 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 (Since R2024a)
`MISRA C:2023 Dir 4.9`	A function should be used in preference to a function-like macro where they are interchangeable (Since R2024a)
`MISRA C:2023 Dir 4.10`	Precautions shall be taken in order to prevent the contents of a header file being included more than once (Since R2024a)
`MISRA C:2023 Dir 4.11`	The validity of values passed to library functions shall be checked (Since R2024a)
`MISRA C:2023 Dir 4.12`	Dynamic memory allocation shall not be used (Since R2024a)
`MISRA C:2023 Dir 4.13`	Functions which are designed to provide operations on a resource should be called in an appropriate sequence (Since R2024a)
`MISRA C:2023 Dir 4.14`	The validity of values received from external sources shall be checked (Since R2024a)
`MISRA C:2023 Dir 4.15`	Evaluation of floating-point expressions shall not lead to the undetected generation of infinities and NaNs (Since R2024a)

Directives — Concurrency Considerations

`MISRA C:2023 Dir 5.1`	There shall be no data races between threads (Since R2024b)
`MISRA C:2023 Dir 5.2`	There shall be no deadlocks between threads (Since R2024b)

1. Standard C Environment

`MISRA C:2023 Rule 1.1`	The program shall contain no violations of the standard C syntax and constraints, and shall not exceed the implementation's translation limits (Since R2024a)
`MISRA C:2023 Rule 1.2`	Language extensions should not be used (Since R2024a)
`MISRA C:2023 Rule 1.3`	There shall be no occurrence of undefined or critical unspecified behaviour (Since R2024a)
`MISRA C:2023 Rule 1.4`	Emergent language features shall not be used (Since R2024a)
`MISRA C:2023 Rule 1.5`	Obsolescent language features shall not be used (Since R2024a)

2. Unused Code

`MISRA C:2023 Rule 2.1`	A project shall not contain unreachable code (Since R2024a)
`MISRA C:2023 Rule 2.2`	A project shall not contain dead code (Since R2024a)
`MISRA C:2023 Rule 2.3`	A project should not contain unused type declarations (Since R2024a)
`MISRA C:2023 Rule 2.4`	A project should not contain unused tag declarations (Since R2024a)
`MISRA C:2023 Rule 2.5`	A project should not contain unused macro definitions (Since R2024a)
`MISRA C:2023 Rule 2.6`	A function should not contain unused label declarations (Since R2024a)
`MISRA C:2023 Rule 2.7`	A function should not contain unused parameters (Since R2024a)

3. Comments

`MISRA C:2023 Rule 3.1`	The character sequences `/*` and `//` shall not be used within a comment (Since R2024a)
`MISRA C:2023 Rule 3.2`	Line-splicing shall not be used in `//` comments (Since R2024a)

4. Character Sets and Lexical Conventions

`MISRA C:2023 Rule 4.1`	Octal and hexadecimal escape sequences shall be terminated (Since R2024a)
`MISRA C:2023 Rule 4.2`	Trigraphs should not be used (Since R2024a)

5. Identifiers

`MISRA C:2023 Rule 5.1`	External identifiers shall be distinct (Since R2024a)
`MISRA C:2023 Rule 5.2`	Identifiers declared in the same scope and name space shall be distinct (Since R2024a)
`MISRA C:2023 Rule 5.3`	An identifier declared in an inner scope shall not hide an identifier declared in an outer scope (Since R2024a)
`MISRA C:2023 Rule 5.4`	Macro identifiers shall be distinct (Since R2024a)
`MISRA C:2023 Rule 5.5`	Identifiers shall be distinct from macro names (Since R2024a)
`MISRA C:2023 Rule 5.6`	A typedef name shall be a unique identifier (Since R2024a)
`MISRA C:2023 Rule 5.7`	A tag name shall be a unique identifier (Since R2024a)
`MISRA C:2023 Rule 5.8`	Identifiers that define objects or functions with external linkage shall be unique (Since R2024a)
`MISRA C:2023 Rule 5.9`	Identifiers that define objects or functions with internal linkage should be unique (Since R2024a)

6. Types

`MISRA C:2023 Rule 6.1`	Bit-fields shall only be declared with an appropriate type (Since R2024a)
`MISRA C:2023 Rule 6.2`	Single-bit named bit-fields shall not be of a signed type (Since R2024a)
`MISRA C:2023 Rule 6.3`	A bit field shall not be declared as a member of a union (Since R2024a)

7. Literals and Constants

`MISRA C:2023 Rule 7.1`	Octal constants shall not be used (Since R2024a)
`MISRA C:2023 Rule 7.2`	A “u” or “U” suffix shall be applied to all integer constants that are represented in an unsigned type (Since R2024a)
`MISRA C:2023 Rule 7.3`	The lowercase character “l” shall not be used in a literal suffix (Since R2024a)
`MISRA C:2023 Rule 7.4`	A string literal shall not be assigned to an object unless the object’s type is “pointer to const-qualified char” (Since R2024a)
`MISRA C:2023 Rule 7.5`	The argument of an integer constant macro shall have an appropriate form (Since R2024a)

8. Declarations and Definitions

`MISRA C:2023 Rule 8.1`	Types shall be explicitly specified (Since R2024a)
`MISRA C:2023 Rule 8.2`	Function types shall be in prototype form with named parameters (Since R2024a)
`MISRA C:2023 Rule 8.3`	All declarations of an object or function shall use the same names and type qualifiers (Since R2024a)
`MISRA C:2023 Rule 8.4`	A compatible declaration shall be visible when an object or function with external linkage is defined (Since R2024a)
`MISRA C:2023 Rule 8.5`	An external object or function shall be declared once in one and only one file (Since R2024a)
`MISRA C:2023 Rule 8.6`	An identifier with external linkage shall have exactly one external definition (Since R2024a)
`MISRA C:2023 Rule 8.7`	Functions and objects should not be defined with external linkage if they are referenced in only one translation unit (Since R2024a)
`MISRA C:2023 Rule 8.8`	The static storage class specifier shall be used in all declarations of objects and functions that have internal linkage (Since R2024a)
`MISRA C:2023 Rule 8.9`	An object should be declared at block scope if its identifier only appears in a single function (Since R2024a)
`MISRA C:2023 Rule 8.10`	An inline function shall be declared with the static storage class (Since R2024a)
`MISRA C:2023 Rule 8.11`	When an array with external linkage is declared, its size should be explicitly specified (Since R2024a)
`MISRA C:2023 Rule 8.12`	Within an enumerator list, the value of an implicitly-specified enumeration constant shall be unique (Since R2024a)
`MISRA C:2023 Rule 8.13`	A pointer should point to a const-qualified type whenever possible (Since R2024a)
`MISRA C:2023 Rule 8.14`	The restrict type qualifier shall not be used (Since R2024a)
`MISRA C:2023 Rule 8.15`	The argument of an integer constant macro shall have an appropriate form (Since R2024a)
`MISRA C:2023 Rule 8.16`	The alignment specification of zero should not appear in an object declaration (Since R2024a)
`MISRA C:2023 Rule 8.17`	At most one explicit alignment specifier should appear in an object declaration (Since R2024a)

9. Initialization

`MISRA C:2023 Rule 9.1`	The value of an object with automatic storage duration shall not be read before it has been set (Since R2024a)
`MISRA C:2023 Rule 9.2`	The initializer for an aggregate or union shall be enclosed in braces (Since R2024a)
`MISRA C:2023 Rule 9.3`	Arrays shall not be partially initialized (Since R2024a)
`MISRA C:2023 Rule 9.4`	An element of an object shall not be initialized more than once (Since R2024a)
`MISRA C:2023 Rule 9.5`	Where designated initializers are used to initialize an array object the size of the array shall be specified explicitly (Since R2024a)

10. The Essential Type Model

`MISRA C:2023 Rule 10.1`	Operands shall not be of an inappropriate essential type (Since R2024a)
`MISRA C:2023 Rule 10.2`	Expressions of essentially character type shall not be used inappropriately in addition and subtraction operations (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 10.4`	Both operands of an operator in which the usual arithmetic conversions are performed shall have the same essential type category (Since R2024a)
`MISRA C:2023 Rule 10.5`	The value of an expression should not be cast to an inappropriate essential type (Since R2024a)
`MISRA C:2023 Rule 10.6`	The value of a composite expression shall not be assigned to an object with wider essential type (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 10.8`	The value of a composite expression shall not be cast to a different essential type category or a wider essential type (Since R2024a)

11. Pointer Type Conversion

`MISRA C:2023 Rule 11.1`	Conversions shall not be performed between a pointer to a function and any other type (Since R2024a)
`MISRA C:2023 Rule 11.2`	Conversions shall not be performed between a pointer to an incomplete type and any other type (Since R2024a)
`MISRA C:2023 Rule 11.3`	A conversion shall not be performed between a pointer to object type and a pointer to a different object type (Since R2024a)
`MISRA C:2023 Rule 11.4`	A conversion should not be performed between a pointer to object and an integer type (Since R2024a)
`MISRA C:2023 Rule 11.5`	A conversion should not be performed from pointer to void into pointer to object (Since R2024a)
`MISRA C:2023 Rule 11.6`	A cast shall not be performed between pointer to void and an arithmetic type (Since R2024a)
`MISRA C:2023 Rule 11.7`	A cast shall not be performed between pointer to object and a non-integer arithmetic type (Since R2024a)
`MISRA C:2023 Rule 11.8`	A conversion shall not remove any `const`, `volatile`, or `_Atomic` qualification from the type pointed to by a pointer (Since R2024a)
`MISRA C:2023 Rule 11.9`	The macro NULL shall be the only permitted form of integer null pointer constant (Since R2024a)

12. Expressions

`MISRA C:2023 Rule 12.1`	The precedence of operators within expressions should be made explicit (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 12.3`	The comma operator should not be used (Since R2024a)
`MISRA C:2023 Rule 12.4`	Evaluation of constant expressions should not lead to unsigned integer wrap-around (Since R2024a)
`MISRA C:2023 Rule 12.5`	The `sizeof` operator shall not have an operand which is a function parameter declared as “array of type” (Since R2024a)

13. Side Effects

`MISRA C:2023 Rule 13.1`	Initializer lists shall not contain persistent side effects (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 13.4`	The result of an assignment operator should not be used (Since R2024a)
`MISRA C:2023 Rule 13.5`	The right hand operand of a logical && or \|\| operator shall not contain persistent side effects (Since R2024a)
`MISRA C:2023 Rule 13.6`	The operand of the sizeof operator shall not contain any expression which has potential side effects (Since R2024a)

14. Control Statement Expressions

`MISRA C:2023 Rule 14.1`	A loop counter shall not have essentially floating type (Since R2024a)
`MISRA C:2023 Rule 14.2`	A for loop shall be well-formed (Since R2024a)
`MISRA C:2023 Rule 14.3`	Controlling expressions shall not be invariant (Since R2024a)
`MISRA C:2023 Rule 14.4`	The controlling expression of an if statement and the controlling expression of an iteration-statement shall have essentially Boolean type (Since R2024a)

15. Control Flow

`MISRA C:2023 Rule 15.1`	The goto statement should not be used (Since R2024a)
`MISRA C:2023 Rule 15.2`	The goto statement shall jump to a label declared later in the same function (Since R2024a)
`MISRA C:2023 Rule 15.3`	Any label referenced by a goto statement shall be declared in the same block, or in any block enclosing the goto statement (Since R2024a)
`MISRA C:2023 Rule 15.4`	There should be no more than one break or goto statement used to terminate any iteration statement (Since R2024a)
`MISRA C:2023 Rule 15.5`	A function should have a single point of exit at the end (Since R2024a)
`MISRA C:2023 Rule 15.6`	The body of an iteration-statement or a selection-statement shall be a compound statement (Since R2024a)
`MISRA C:2023 Rule 15.7`	All if … else if constructs shall be terminated with an else statement (Since R2024a)

16. Switch Statements

`MISRA C:2023 Rule 16.1`	All switch statements shall be well-formed (Since R2024a)
`MISRA C:2023 Rule 16.2`	A switch label shall only be used when the most closely-enclosing compound statement is the body of a switch statement (Since R2024a)
`MISRA C:2023 Rule 16.3`	An unconditional break statement shall terminate every switch-clause (Since R2024a)
`MISRA C:2023 Rule 16.4`	Every switch statement shall have a default label (Since R2024a)
`MISRA C:2023 Rule 16.5`	A default label shall appear as either the first or the last switch label of a switch statement (Since R2024a)
`MISRA C:2023 Rule 16.6`	Every switch statement shall have at least two switch-clauses (Since R2024a)
`MISRA C:2023 Rule 16.7`	A switch-expression shall not have essentially Boolean type (Since R2024a)

17. Functions

`MISRA C:2023 Rule 17.1`	The standard header file <stdarg.h> shall not be used (Since R2024a)
`MISRA C:2023 Rule 17.2`	Functions shall not call themselves, either directly or indirectly (Since R2024a)
`MISRA C:2023 Rule 17.3`	A function shall not be declared implicitly (Since R2024a)
`MISRA C:2023 Rule 17.4`	All exit paths from a function with non-void return type shall have an explicit return statement with an expression (Since R2024a)
`MISRA C:2023 Rule 17.5`	The function argument corresponding to a parameter declared to have an array type shall have an appropriate number of elements (Since R2024a)
`MISRA C:2023 Rule 17.6`	The declaration of an array parameter shall not contain the static keyword between the [ ] (Since R2024a)
`MISRA C:2023 Rule 17.7`	The value returned by a function having non-void return type shall be used (Since R2024a)
`MISRA C:2023 Rule 17.8`	A function parameter should not be modified (Since R2024a)
`MISRA C:2023 Rule 17.9`	A function declared with a `_Noreturn` function specifier shall not return to its caller (Since R2024a)
`MISRA C:2023 Rule 17.10`	A function declared with a `_Noreturn` function specifier shall have void return type (Since R2024a)
`MISRA C:2023 Rule 17.11`	A function that never returns should be declared with a `_Noreturn` function specifier (Since R2024a)
`MISRA C:2023 Rule 17.12`	A function identifier should only be used with either a preceding `&`, or with a parenthesized parameter list (Since R2024a)
`MISRA C:2023 Rule 17.13`	A function type shall not be type qualified (Since R2024a)

18. Pointers and Arrays

`MISRA C:2023 Rule 18.1`	A pointer resulting from arithmetic on a pointer operand shall address an element of the same array as that pointer operand (Since R2024a)
`MISRA C:2023 Rule 18.2`	Subtraction between pointers shall only be applied to pointers that address elements of the same array (Since R2024a)
`MISRA C:2023 Rule 18.3`	The relational operators >, >=, < and <= shall not be applied to expressions of pointer type except where they point into the same object (Since R2024a)
`MISRA C:2023 Rule 18.4`	The +, -, += and -= operators should not be applied to an expression of pointer type (Since R2024a)
`MISRA C:2023 Rule 18.5`	Declarations should contain no more than two levels of pointer nesting (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 18.7`	Flexible array members shall not be declared (Since R2024a)
`MISRA C:2023 Rule 18.8`	Variable-length arrays shall not be used (Since R2024a)
`MISRA C:2023 Rule 18.9`	An object with temporary lifetime shall not undergo array-to-pointer conversion (Since R2024a)

19. Overlapping Storage

`MISRA C:2023 Rule 19.1`	An object shall not be assigned or copied to an overlapping object (Since R2024a)
`MISRA C:2023 Rule 19.2`	The union keyword should not be used (Since R2024a)

20. Preprocessing Directives

`MISRA C:2023 Rule 20.1`	#include directives should only be preceded by preprocessor directives or comments (Since R2024a)
`MISRA C:2023 Rule 20.2`	The ', " or \ characters and the /* or // character sequences shall not occur in a header file name (Since R2024a)
`MISRA C:2023 Rule 20.3`	The #include directive shall be followed by either a <filename> or "filename" sequence (Since R2024a)
`MISRA C:2023 Rule 20.4`	A macro shall not be defined with the same name as a keyword (Since R2024a)
`MISRA C:2023 Rule 20.5`	#undef should not be used (Since R2024a)
`MISRA C:2023 Rule 20.6`	Tokens that look like a preprocessing directive shall not occur within a macro argument (Since R2024a)
`MISRA C:2023 Rule 20.7`	Expressions resulting from the expansion of macro parameters shall be enclosed in parentheses (Since R2024a)
`MISRA C:2023 Rule 20.8`	The controlling expression of a #if or #elif preprocessing directive shall evaluate to 0 or 1 (Since R2024a)
`MISRA C:2023 Rule 20.9`	All identifiers used in the controlling expression of #if or #elif preprocessing directives shall be #define'd before evaluation (Since R2024a)
`MISRA C:2023 Rule 20.10`	The # and ## preprocessor operators should not be used (Since R2024a)
`MISRA C:2023 Rule 20.11`	A macro parameter immediately following a # operator shall not immediately be followed by a ## operator (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 20.13`	A line whose first token is # shall be a valid preprocessing directive (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)

21. Standard Libraries

`MISRA C:2023 Rule 21.1`	#define and #undef shall not be used on a reserved identifier or reserved macro name (Since R2024a)
`MISRA C:2023 Rule 21.2`	A reserved identifier or reserved macro name shall not be declared (Since R2024a)
`MISRA C:2023 Rule 21.3`	The memory allocation and deallocation functions of `<stdlib.h>` shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.4`	The standard header file <setjmp.h> shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.5`	The standard header file <signal.h> shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.6`	The Standard Library input/output functions shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.7`	The Standard Library functions `atof`, `atoi`, `atol`, and `atoll` functions of `<stdlib.h>` shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.8`	The Standard Library termination functions of `<stdlib.h>` shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.9`	The Standard Library library functions `bsearch` and `qsort` of `<stdlib.h>` shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.10`	The Standard Library time and date functions shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.11`	The standard header file <tgmath.h> should not be used (Since R2024a)
`MISRA C:2023 Rule 21.12`	The standard header file `<fenv.h>` shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.13`	Any value passed to a function in `<ctype.h>` shall be representable as an `unsigned char` or be the value EOF (Since R2024a)
`MISRA C:2023 Rule 21.14`	The Standard Library function `memcmp` shall not be used to compare null terminated strings (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 21.17`	Use of the string handling function from `<string.h>` shall not result in accesses beyond the bounds of the objects referenced by their pointer parameters (Since R2024a)
`MISRA C:2023 Rule 21.18`	The `size_t` argument passed to any function in `<string.h>` shall have an appropriate value (Since R2024a)
`MISRA C:2023 Rule 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 (Since R2024a)
`MISRA C:2023 Rule 21.20`	The pointer returned by the Standard Library functions `asctime`, `ctime`, `gmtime`, `localtime`, `localeconv`, `getenv`, `setlocale` or `strerror` shall not be used following a subsequent call to the same function (Since R2024a)
`MISRA C:2023 Rule 21.21`	The Standard Library function `system` of `<stdlib.h>` shall not be used (Since R2024a)
`MISRA C:2023 Rule 21.22`	All operand arguments to any type-generic macros declared in <tgmath.h> shall have an appropriate essential type (Since R2024a)
`MISRA C:2023 Rule 21.23`	All operand arguments to any multi-argument type-generic macros declared in <tgmath.h> shall have the same standard type (Since R2024a)
`MISRA C:2023 Rule 21.24`	The random number generator functions of `<stdlib.h>` shall not be used (Since R2024a)

22. Resources

`MISRA C:2023 Rule 22.1`	All resources obtained dynamically by means of Standard Library functions shall be explicitly released (Since R2024a)
`MISRA C:2023 Rule 22.2`	A block of memory shall only be freed if it was allocated by means of a Standard Library function (Since R2024a)
`MISRA C:2023 Rule 22.3`	The same file shall not be open for read and write access at the same time on different streams (Since R2024a)
`MISRA C:2023 Rule 22.4`	There shall be no attempt to write to a stream which has been opened as read-only (Since R2024a)
`MISRA C:2023 Rule 22.5`	A pointer to a `FILE` object shall not be dereferenced (Since R2024a)
`MISRA C:2023 Rule 22.6`	The value of a pointer to a `FILE` shall not be used after the associated stream has been closed (Since R2024a)
`MISRA C:2023 Rule 22.7`	The macro `EOF` shall only be compared with the unmodified return value from any Standard Library function capable of returning `EOF` (Since R2024a)
`MISRA C:2023 Rule 22.8`	The value of `errno` shall be set to zero prior to a call to an `errno`-setting-function (Since R2024a)
`MISRA C:2023 Rule 22.9`	The value of `errno` shall be tested against zero after calling an `errno`-setting function (Since R2024a)
`MISRA C:2023 Rule 22.10`	The value of `errno` shall only be tested when the last function to be called was an `errno`-setting function (Since R2024a)
`MISRA C:2023 Rule 22.11`	A thread that was previously either joined or detached shall not be subsequently joined nor detached (Since R2024b)
`MISRA C:2023 Rule 22.15`	Thread synchronization objects and thread-specific storage pointers shall not be destroyed until after all threads accessing them have terminated (Since R2024b)
`MISRA C:2023 Rule 22.16`	All mutex objects locked by a thread shall be explicitly unlocked by the same thread (Since R2024b)
`MISRA C:2023 Rule 22.17`	No thread shall unlock a mutex or call `cnd_wait()` or `cnd_timedwait()` for a mutex it has not locked before (Since R2024b)

23. Generic Selections

`MISRA C:2023 Rule 23.1`	A generic selection should only be expanded from a macro (Since R2024a)
`MISRA C:2023 Rule 23.2`	A generic selection that is not expanded from a macro shall not contain potential side effects in the controlling expression (Since R2024a)
`MISRA C:2023 Rule 23.3`	A generic selection should contain at least one non-default association (Since R2024a)
`MISRA C:2023 Rule 23.4`	A generic association shall list an appropriate type (Since R2024a)
`MISRA C:2023 Rule 23.5`	A generic selection should not depend on implicit pointer type conversion (Since R2024a)
`MISRA C:2023 Rule 23.6`	The controlling expression of a generic selection shall have an essential type that matches its standard type (Since R2024a)
`MISRA C:2023 Rule 23.7`	A generic selection that is expanded from a macro should evaluate its argument only once (Since R2024a)
`MISRA C:2023 Rule 23.8`	A default association shall appear as either the first or the last association of a generic selection (Since R2024a)

Topics

Polyspace Support for MISRA C:2023

Polyspace Support for Coding Standards
Check the Polyspace support for different coding standards.
Check for and Review Coding Standard Violations
Check for violations of AUTOSAR C++14, CERT^® C, CERT C++, CWE, MISRA C, MISRA C++, JSF AV C++, or ISO-17961 standards with Polyspace Bug Finder.
Import Justifications from Older Standard to Newer Standard
Import existing review information when migrating from the older coding standard.
Required or Mandatory MISRA Coding Rules Supported by Polyspace Bug Finder
Find out the required rules in various MISRA coding standards that Polyspace supports.
Decidable MISRA Coding Rules Supported by Polyspace Bug Finder
Find out the decidable rules in various MISRA coding standards that Polyspace supports.

MISRA C:2023 Subsets

Coding Rule Subsets Checked Early in Analysis
Adjust your coding rules checking for a faster analysis.
Software Quality Objective Subsets for MISRA Coding Standards
MISRA C and C++ rules that help address design issues.

Specific MISRA C:2023 Rules

Avoid Violations of MISRA C Rules 8.x
Avoid conflicting declarations or unintended modification of variables.
Essential Types in MISRA C Rules 10.x
Similar data types that are treated as essentially similar by MISRA C Rules 10.x.