MISRA C:2025 Directives and Rules

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

Polyspace can check your code against the MISRA C™:2025 coding rules and directives.

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 -misra-c-2025 to activate subsets of the rules.

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

MISRA C:2025 D1.1Any implementation-defined behavior on which the output of the program depends shall be documented and understood (Since R2026b)
MISRA C:2025 D2.1All source files shall compile without any compilation errors (Since R2026b)
MISRA C:2025 D4.1Run-time failures shall be minimized (Since R2026b)
MISRA C:2025 D4.10Precautions shall be taken in order to prevent the contents of a header file being included more than once (Since R2026b)
MISRA C:2025 D4.11The validity of values passed to library functions shall be checked (Since R2026b)
MISRA C:2025 D4.12Dynamic memory allocation shall not be used (Since R2026b)
MISRA C:2025 D4.13Functions which are designed to provide operations on a resource should be called in an appropriate sequence (Since R2026b)
MISRA C:2025 D4.14The validity of values received from external sources shall be checked (Since R2026b)
MISRA C:2025 D4.15Evaluation of floating-point expressions shall not lead to the undetected generation of infinities and NaNs (Since R2026b)
MISRA C:2025 D4.3Assembly language shall be encapsulated and isolated (Since R2026b)
MISRA C:2025 D4.4Sections of code should not be "commented out" (Since R2026b)
MISRA C:2025 D4.5Identifiers in the same name space with overlapping visibility should be typographically unambiguous (Since R2026b)
MISRA C:2025 D4.6 typedefs that indicate size and signedness should be used in place of the basic numerical types (Since R2026b)
MISRA C:2025 D4.7If a function returns error information, then that error information shall be tested (Since R2026b)
MISRA C:2025 D4.8If a pointer to a structure or union is never dereferenced within a translation unit, then the implementation of the object should be hidden (Since R2026b)
MISRA C:2025 D4.9A function should be used in preference to a function-like macro where they are interchangeable (Since R2026b)
MISRA C:2025 D5.1There shall be no data races between threads (Since R2026b)
MISRA C:2025 D5.2There shall be no deadlocks between threads (Since R2026b)
MISRA C:2025 D5.3There shall be no dynamic thread creation (Since R2026b)
MISRA C:2025 Rule 1.1The program shall contain no violations of the standard C syntax and constraints, and shall not exceed the implementation's translation limits (Since R2026b)
MISRA C:2025 Rule 1.3There shall be no occurrence of undefined or critical unspecified behaviour (Since R2026b)
MISRA C:2025 Rule 1.4Emergent language features shall not be used (Since R2026b)
MISRA C:2025 Rule 1.5Obsolescent language features shall not be used (Since R2026b)
MISRA C:2025 Rule 2.1A project shall not contain unreachable code (Since R2026b)
MISRA C:2025 Rule 2.2A project shall not contain dead code (Since R2026b)
MISRA C:2025 Rule 2.3A project should not contain unused type declarations (Since R2026b)
MISRA C:2025 Rule 2.4A project should not contain unused tag declarations (Since R2026b)
MISRA C:2025 Rule 2.5A project should not contain unused macro definitions (Since R2026b)
MISRA C:2025 Rule 2.6A function should not contain unused label declarations (Since R2026b)
MISRA C:2025 Rule 2.7A function should not contain unused parameters (Since R2026b)
MISRA C:2025 Rule 2.8A project should not contain unused object definitions (Since R2026b)
MISRA C:2025 Rule 3.1The character sequences /* and // shall not be used within a comment (Since R2026b)
MISRA C:2025 Rule 3.2Line-splicing shall not be used in // comments (Since R2026b)
MISRA C:2025 Rule 4.1Octal and hexadecimal escape sequences shall be terminated (Since R2026b)
MISRA C:2025 Rule 4.2Trigraphs should not be used (Since R2026b)
MISRA C:2025 Rule 5.1External identifiers shall be distinct (Since R2026b)
MISRA C:2025 Rule 5.2Identifiers declared in the same scope and name space shall be distinct (Since R2026b)
MISRA C:2025 Rule 5.3An identifier declared in an inner scope shall not hide an identifier declared in an outer scope (Since R2026b)
MISRA C:2025 Rule 5.4Macro identifiers shall be distinct (Since R2026b)
MISRA C:2025 Rule 5.5Identifiers shall be distinct from macro names (Since R2026b)
MISRA C:2025 Rule 5.6A typedef name shall be a unique identifier (Since R2026b)
MISRA C:2025 Rule 5.7A tag name shall be a unique identifier (Since R2026b)
MISRA C:2025 Rule 5.8Identifiers that define objects or functions with external linkage shall be unique (Since R2026b)
MISRA C:2025 Rule 5.9Identifiers that define objects or functions with internal linkage should be unique (Since R2026b)
MISRA C:2025 Rule 6.1Bit-fields shall only be declared with an appropriate type (Since R2026b)
MISRA C:2025 Rule 6.2Single-bit named bit-fields shall not be of a signed type (Since R2026b)
MISRA C:2025 Rule 6.3A bit-field shall not be declared as a member of a union (Since R2026b)
MISRA C:2025 Rule 7.6The small integer variants of the minimum-width integer constant macros shall not be used (Since R2026b)
MISRA C:2025 Rule 7.1Octal constants shall not be used (Since R2026b)
MISRA C:2025 Rule 7.2A “u” or “U” suffix shall be applied to all integer constants that are represented in an unsigned type (Since R2026b)
MISRA C:2025 Rule 7.3The lowercase character “l” shall not be used in a literal suffix (Since R2026b)
MISRA C:2025 Rule 7.4A string literal shall not be assigned to an object unless the object’s type is “pointer to const-qualified char” (Since R2026b)
MISRA C:2025 Rule 7.5The argument of an integer constant macro shall have an appropriate form (Since R2026b)
MISRA C:2025 Rule 8.1Types shall be explicitly specified (Since R2026b)
MISRA C:2025 Rule 8.10An inline function shall be declared with the static storage class (Since R2026b)
MISRA C:2025 Rule 8.11When an array with external linkage is declared, its size should be explicitly specified (Since R2026b)
MISRA C:2025 Rule 8.12Within an enumerator list, the value of an implicitly-specified enumeration constant shall be unique (Since R2026b)
MISRA C:2025 Rule 8.13A pointer should point to a const-qualified type whenever possible (Since R2026b)
MISRA C:2025 Rule 8.14The restrict type qualifier shall not be used (Since R2026b)
MISRA C:2025 Rule 8.15All declarations of an object with an explicit alignment specification shall specify the same alignment (Since R2026b)
MISRA C:2025 Rule 8.16The alignment specification of zero should not appear in an object declaration (Since R2026b)
MISRA C:2025 Rule 8.17At most one explicit alignment specifier should appear in an object declaration (Since R2026b)
MISRA C:2025 Rule 8.18There shall be no tentative definitions in a header file (Since R2026b)
MISRA C:2025 Rule 8.19There should be no external declarations in a source file (Since R2026b)
MISRA C:2025 Rule 8.2Function types shall be in prototype form with named parameters (Since R2026b)
MISRA C:2025 Rule 8.3All declarations of an object or function shall use the same names and type qualifiers (Since R2026b)
MISRA C:2025 Rule 8.4A compatible declaration shall be visible when an object or function with external linkage is defined (Since R2026b)
MISRA C:2025 Rule 8.5An external object or function shall be declared once in one and only one file (Since R2026b)
MISRA C:2025 Rule 8.6An identifier with external linkage shall have exactly one external definition (Since R2026b)
MISRA C:2025 Rule 8.7Functions and objects should not be defined with external linkage if they are referenced in only one translation unit (Since R2026b)
MISRA C:2025 Rule 8.8The static storage class specifier shall be used in all declarations of objects and functions that have internal linkage (Since R2026b)
MISRA C:2025 Rule 8.9An object should be declared at block scope if its identifier only appears in a single function (Since R2026b)
MISRA C:2025 Rule 9.6An initializer using chained designators shall not contain initializers without designators (Since R2026b)
MISRA C:2025 Rule 9.7Atomic objects shall be appropriately initialized before being accessed (Since R2026b)
MISRA C:2025 Rule 9.1The value of an object with automatic storage duration shall not be read before it has been set (Since R2026b)
MISRA C:2025 Rule 9.2The initializer for an aggregate or union shall be enclosed in braces (Since R2026b)
MISRA C:2025 Rule 9.3Arrays shall not be partially initialized (Since R2026b)
MISRA C:2025 Rule 9.4An element of an object shall not be initialized more than once (Since R2026b)
MISRA C:2025 Rule 9.5Where designated initializers are used to initialize an array object the size of the array shall be specified explicitly (Since R2026b)
MISRA C:2025 Rule 10.1Operands shall not be of an inappropriate essential type (Since R2026b)
MISRA C:2025 Rule 10.2Expressions of essentially character type shall not be used inappropriately in addition and subtraction operations (Since R2026b)
MISRA C:2025 Rule 10.3The value of an expression shall not be assigned to an object with a narrower essential type or of a different essential type category (Since R2026b)
MISRA C:2025 Rule 10.4Both operands of an operator in which the usual arithmetic conversions are performed shall have the same essential type category (Since R2026b)
MISRA C:2025 Rule 10.5The value of an expression should not be cast to an inappropriate essential type (Since R2026b)
MISRA C:2025 Rule 10.6The value of a composite expression shall not be assigned to an object with wider essential type (Since R2026b)
MISRA C:2025 Rule 10.7If a composite expression is used as one operand of an operator in which the usual arithmetic conversions are performed then the other operand shall not have wider essential type (Since R2026b)
MISRA C:2025 Rule 10.8The value of a composite expression shall not be cast to a different essential type category or a wider essential type (Since R2026b)
MISRA C:2025 Rule 11.1Conversions shall not be performed between a pointer to a function and any other type (Since R2026b)
MISRA C:2025 Rule 11.10The _Atomic qualifier shall not be applied to the incomplete type void (Since R2026b)
MISRA C:2025 Rule 11.11Pointers shall not be implicitly compared to NULL (Since R2026b)
MISRA C:2025 Rule 11.2Conversions shall not be performed between a pointer to an incomplete type and any other type (Since R2026b)
MISRA C:2025 Rule 11.3A conversion shall not be performed between a pointer to object type and a pointer to a different object type (Since R2026b)
MISRA C:2025 Rule 11.4A conversion shall not be performed between a pointer to object and an arithmetic type (Since R2026b)
MISRA C:2025 Rule 11.5A conversion should not be performed from pointer to void into pointer to object (Since R2026b)
MISRA C:2025 Rule 11.6A cast shall not be performed between pointer to void and an arithmetic type (Since R2026b)
MISRA C:2025 Rule 11.8A conversion shall not remove any const, volatile, or _Atomic qualification from the type pointed to by a pointer (Since R2026b)
MISRA C:2025 Rule 11.9The macro NULL shall be the only permitted form of integer null pointer constant (Since R2026b)
MISRA C:2025 Rule 12.6Structure and union members of atomic objects shall not be directly accessed (Since R2026b)
MISRA C:2025 Rule 12.1The precedence of operators within expressions should be made explicit (Since R2026b)
MISRA C:2025 Rule 12.2The right hand operand of a shift operator shall lie in the range zero to one less than the width in bits of the essential type of the left hand operand (Since R2026b)
MISRA C:2025 Rule 12.3The comma operator should not be used (Since R2026b)
MISRA C:2025 Rule 12.4Evaluation of constant expressions should not lead to unsigned integer wrap-around (Since R2026b)
MISRA C:2025 Rule 12.5The sizeof operator shall not have an operand which is a function parameter declared as “array of type” (Since R2026b)
MISRA C:2025 Rule 13.1Initializer lists shall not contain persistent side effects (Since R2026b)
MISRA C:2025 Rule 13.2The value of an expression and its persistent side effects shall be the same under all permitted evaluation orders and shall be independent from thread interleaving (Since R2026b)
MISRA C:2025 Rule 13.3A full expression containing an increment (++) or decrement (--) operator should have no other potential side effects other than that caused by the increment or decrement operator (Since R2026b)
MISRA C:2025 Rule 13.4The result of an assignment operator should not be used (Since R2026b)
MISRA C:2025 Rule 13.5The right hand operand of a logical && or || operator shall not contain persistent side effects (Since R2026b)
MISRA C:2025 Rule 13.6The operand of the sizeof operator shall not contain any expression which has potential side effects (Since R2026b)
MISRA C:2025 Rule 14.1A loop counter shall not have essentially floating type (Since R2026b)
MISRA C:2025 Rule 14.2A for loop shall be well-formed (Since R2026b)
MISRA C:2025 Rule 14.3Controlling expressions shall not be invariant (Since R2026b)
MISRA C:2025 Rule 14.4The controlling expression of an if statement and the controlling expression of an iteration-statement shall have essentially Boolean type (Since R2026b)
MISRA C:2025 Rule 15.1The goto statement should not be used (Since R2026b)
MISRA C:2025 Rule 15.2The goto statement shall jump to a label declared later in the same function (Since R2026b)
MISRA C:2025 Rule 15.3Any label referenced by a goto statement shall be declared in the same block, or in any block enclosing the goto statement (Since R2026b)
MISRA C:2025 Rule 15.4There should be no more than one break or goto statement used to terminate any iteration statement (Since R2026b)
MISRA C:2025 Rule 15.5A function should have a single point of exit at the end (Since R2026b)
MISRA C:2025 Rule 15.6The body of an iteration-statement or a selection-statement shall be a compound statement (Since R2026b)
MISRA C:2025 Rule 15.7All if ... else if constructs shall be terminated with an else statement (Since R2026b)
MISRA C:2025 Rule 16.1All switch statements shall be well-formed (Since R2026b)
MISRA C:2025 Rule 16.2A switch label shall only be used when the most closely-enclosing compound statement is the body of a switch statement (Since R2026b)
MISRA C:2025 Rule 16.3Every switch-clause shall be appropriately terminated (Since R2026b)
MISRA C:2025 Rule 16.4Every switch statement shall have a default label (Since R2026b)
MISRA C:2025 Rule 16.5A default label shall appear as either the first or the last switch label of a switch statement (Since R2026b)
MISRA C:2025 Rule 16.6Every switch statement shall have at least two switch-clauses (Since R2026b)
MISRA C:2025 Rule 16.7A switch-expression shall not have essentially Boolean type (Since R2026b)
MISRA C:2025 Rule 17.1The standard header file <stdarg.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 17.10A function declared with a _Noreturn function specifier shall have void return type (Since R2026b)
MISRA C:2025 Rule 17.11A function that never returns should be declared with a _Noreturn function specifier (Since R2026b)
MISRA C:2025 Rule 17.12A function identifier should only be used with either a preceding &, or with a parenthesized parameter list (Since R2026b)
MISRA C:2025 Rule 17.13A function type shall not be type qualified (Since R2026b)
MISRA C:2025 Rule 17.2Functions shall not call themselves, either directly or indirectly (Since R2026b)
MISRA C:2025 Rule 17.3A function shall not be declared implicitly (Since R2026b)
MISRA C:2025 Rule 17.4All exit paths from a function with non-void return type shall have an explicit return statement with an expression (Since R2026b)
MISRA C:2025 Rule 17.5The function argument corresponding to a parameter declared to have an array type shall have an appropriate number of elements (Since R2026b)
MISRA C:2025 Rule 17.7The value returned by a function having non-void return type shall be used (Since R2026b)
MISRA C:2025 Rule 17.8A function parameter should not be modified (Since R2026b)
MISRA C:2025 Rule 17.9A function declared with a _Noreturn function specifier shall not return to its caller (Since R2026b)
MISRA C:2025 Rule 18.1A pointer resulting from arithmetic on a pointer operand shall address an element of the same array as that pointer operand (Since R2026b)
MISRA C:2025 Rule 18.10Pointers to variably-modified array types shall not be used (Since R2026b)
MISRA C:2025 Rule 18.2Subtraction between pointers shall only be applied to pointers that address elements of the same array (Since R2026b)
MISRA C:2025 Rule 18.3The relational operators >, >=, < and <= shall not be applied to expressions of pointer type except where they point into the same object (Since R2026b)
MISRA C:2025 Rule 18.4The +, -, += and -= operators should not be applied to an expression of pointer type (Since R2026b)
MISRA C:2025 Rule 18.5Declarations should contain no more than two levels of pointer nesting (Since R2026b)
MISRA C:2025 Rule 18.6The 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 R2026b)
MISRA C:2025 Rule 18.7Flexible array members shall not be declared (Since R2026b)
MISRA C:2025 Rule 18.8Variable-length arrays shall not be used (Since R2026b)
MISRA C:2025 Rule 18.9An object with temporary lifetime shall not undergo array-to-pointer conversion (Since R2026b)
MISRA C:2025 Rule 19.1An object shall not be assigned or copied to an overlapping object (Since R2026b)
MISRA C:2025 Rule 19.2The union keyword should not be used (Since R2026b)
MISRA C:2025 Rule 19.3A union member shall not be read unless it has been previously set (Since R2026b)
MISRA C:2025 Rule 20.1#include directives should only be preceded by preprocessor directives or comments (Since R2026b)
MISRA C:2025 Rule 20.10The # and ## preprocessor operators should not be used (Since R2026b)
MISRA C:2025 Rule 20.11A macro parameter immediately following a # operator shall not immediately be followed by a ## operator (Since R2026b)
MISRA C:2025 Rule 20.12A macro parameter used as an operand to the # or ## operators, which is itself subject to further macro replacement, shall only be used as an operand to these operators (Since R2026b)
MISRA C:2025 Rule 20.13A line whose first token is # shall be a valid preprocessing directive (Since R2026b)
MISRA C:2025 Rule 20.14All #else, #elif and #endif preprocessor directives shall reside in the same file as the #if, #ifdef or #ifndef directive to which they are related (Since R2026b)
MISRA C:2025 Rule 20.2The ', " or \ characters and the /* or // character sequences shall not occur in a header file name (Since R2026b)
MISRA C:2025 Rule 20.3The #include directive shall be followed by either a <filename> or "filename" sequence (Since R2026b)
MISRA C:2025 Rule 20.4A macro shall not be defined with the same name as a keyword (Since R2026b)
MISRA C:2025 Rule 20.5#undef should not be used (Since R2026b)
MISRA C:2025 Rule 20.6Tokens that look like a preprocessing directive shall not occur within a macro argument (Since R2026b)
MISRA C:2025 Rule 20.7Tokens that look like a preprocessing directive shall not occur within a macro argument (Since R2026b)
MISRA C:2025 Rule 20.8The controlling expression of a #if or #elif preprocessing directive shall evaluate to 0 or 1 (Since R2026b)
MISRA C:2025 Rule 20.9All identifiers used in the controlling expression of #if or #elif preprocessing directives shall be #define'd before evaluation (Since R2026b)
MISRA C:2025 Rule 21.25All memory synchronization operations shall be executed in sequentially consistent order (Since R2026b)
MISRA C:2025 Rule 21.10The Standard Library time and date functions shall not be used (Since R2026b)
MISRA C:2025 Rule 21.11The standard header file <tgmath.h> should not be used (Since R2026b)
MISRA C:2025 Rule 21.12The standard header file <fenv.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.13Any value passed to a function in <ctype.h> shall be representable as an unsigned char or be the value EOF (Since R2026b)
MISRA C:2025 Rule 21.14The Standard Library function memcmp shall not be used to compare null terminated strings (Since R2026b)
MISRA C:2025 Rule 21.15The pointer arguments to the Standard Library functions memcpy, memmove and memcmp shall be pointers to qualified or unqualified versions of compatible types (Since R2026b)
MISRA C:2025 Rule 21.16The pointer arguments to the Standard Library function memcmp shall point to either a pointer type, an essentially signed type, an essentially unsigned type, an essentially Boolean type or an essentially enum type (Since R2026b)
MISRA C:2025 Rule 21.17Use 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 R2026b)
MISRA C:2025 Rule 21.18The size_t argument passed to any function in <string.h> shall have an appropriate value (Since R2026b)
MISRA C:2025 Rule 21.19The pointers returned by the Standard Library functions localeconv, getenv, setlocale or strerror shall only be used as if they have pointer to const-qualified type (Since R2026b)
MISRA C:2025 Rule 21.20The pointer returned by the Standard Library functions asctime, ctime, gmtime, localtime, localeconv, getenv, setlocale or strerror shall not be used following a subsequent call to the same function (Since R2026b)
MISRA C:2025 Rule 21.21The Standard Library function system of <stdlib.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.22All operand arguments to any type-generic macros declared in <tgmath.h> shall have an appropriate essential type (Since R2026b)
MISRA C:2025 Rule 21.23All operand arguments to any multi-argument type-generic macros declared in <tgmath.h> shall have the same standard type (Since R2026b)
MISRA C:2025 Rule 21.24The random number generator functions of <stdlib.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.26The Standard Library function mtx_timedlock() shall only be invoked on mutex objects of appropriate mutex type (Since R2026b)
MISRA C:2025 Rule 21.3The memory allocation and deallocation functions of <stdlib.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.4The standard header file <setjmp.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.5The standard header file <signal.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.6The Standard Library input/output functions shall not be used (Since R2026b)
MISRA C:2025 Rule 21.7The Standard Library functions atof, atoi, atol, and atoll functions of <stdlib.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.8The Standard Library termination functions of <stdlib.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 21.9The Standard Library library functions bsearch and qsort of <stdlib.h> shall not be used (Since R2026b)
MISRA C:2025 Rule 22.13Thread objects, thread synchronization objects and thread-specific storage pointers shall have appropriate storage duration (Since R2026b)
MISRA C:2025 Rule 22.14Thread synchronization objects shall be initialized before being accessed (Since R2026b)
MISRA C:2025 Rule 22.1All resources obtained dynamically by means of Standard Library functions shall be explicitly released (Since R2026b)
MISRA C:2025 Rule 22.10The value of errno shall only be tested when the last function to be called was an errno-setting function (Since R2026b)
MISRA C:2025 Rule 22.11A thread that was previously either joined or detached shall not be subsequently joined nor detached (Since R2026b)
MISRA C:2025 Rule 22.12Thread objects, thread synchronization objects, and thread-specific storage pointers shall only be accessed by the appropriate Standard Library functions (Since R2026b)
MISRA C:2025 Rule 22.15Thread synchronization objects and thread-specific storage pointers shall not be destroyed until after all threads accessing them have terminated (Since R2026b)
MISRA C:2025 Rule 22.16All mutex objects locked by a thread shall be explicitly unlocked by the same thread (Since R2026b)
MISRA C:2025 Rule 22.17No thread shall unlock a mutex or call cnd_wait() or cnd_timedwait() for a mutex it has not locked before (Since R2026b)
MISRA C:2025 Rule 22.18Non-recursive mutexes shall not be recursively locked (Since R2026b)
MISRA C:2025 Rule 22.19A condition variable shall be associated with at most one mutex object (Since R2026b)
MISRA C:2025 Rule 22.2A block of memory shall only be freed if it was allocated by means of a Standard Library function (Since R2026b)
MISRA C:2025 Rule 22.20Thread-specific storage pointers shall be created before being accessed (Since R2026b)
MISRA C:2025 Rule 22.3The same file shall not be open for read and write access at the same time on different streams (Since R2026b)
MISRA C:2025 Rule 22.4There shall be no attempt to write to a stream which has been opened as read-only (Since R2026b)
MISRA C:2025 Rule 22.5A pointer to a FILE object shall not be dereferenced (Since R2026b)
MISRA C:2025 Rule 22.6The value of a pointer to a FILE shall not be used after the associated stream has been closed (Since R2026b)
MISRA C:2025 Rule 22.7The macro EOF shall only be compared with the unmodified return value from any Standard Library function capable of returning EOF (Since R2026b)
MISRA C:2025 Rule 22.8The value of errno shall be set to zero prior to a call to an errno-setting-function (Since R2026b)
MISRA C:2025 Rule 22.9The value of errno shall be tested against zero after calling an errno-setting function (Since R2026b)
MISRA C:2025 Rule 23.1A generic selection should only be expanded from a macro (Since R2026b)
MISRA C:2025 Rule 23.2A generic selection that is not expanded from a macro shall not contain potential side effects in the controlling expression (Since R2026b)
MISRA C:2025 Rule 23.3A generic selection should contain at least one non-default association (Since R2026b)
MISRA C:2025 Rule 23.4A generic association shall list an appropriate type (Since R2026b)
MISRA C:2025 Rule 23.5A generic selection should not depend on implicit pointer type conversion (Since R2026b)
MISRA C:2025 Rule 23.6The controlling expression of a generic selection shall have an essential type that matches its standard type (Since R2026b)
MISRA C:2025 Rule 23.7A generic selection that is expanded from a macro should evaluate its argument only once (Since R2026b)
MISRA C:2025 Rule 23.8A default association shall appear as either the first or the last association of a generic selection (Since R2026b)

Topics

Polyspace Support for MISRA C:2025

MISRA C:2025 Subsets

Specific MISRA C:2025 Rules