Directives et règles MISRA C:2023

Liste et description des directives et règles MISRA™:2023 supportées par Polyspace®

Polyspace peut vérifier votre code par rapport aux règles de codage MISRA C™:2023 et à aux directives. La norme MISRA C:2023 regroupe les directives suivantes :

  • Règles et directives MISRA C:2012.

  • Clarifications ajoutées aux rectificatifs techniques 1 (TC1) et 2 (TC2).

  • Nouvelles règles et modifications ajoutées aux amendements 1 (AMD1), 2 (AMD2), 3 (AMD3) et 4 (AMD4).

Chaque directive est classée dans l'une des catégories suivantes : obligatoire, requise ou conseillée. Lorsque vous configurez le contrôle des règles, vous pouvez choisir de contrôler des sous-ensembles de ces catégories. Utilisez l'option d’analyse Check MISRA C:2023 (-misra-c-2023) pour activer des sous-ensembles de règles.

Dans le cas d’un code généré automatiquement, certaines règles changent de catégorie, y compris pour une catégorie supplémentaire : la lisibilité. L’option Use generated code requirements (-misra-c-2023-agc-mode) active la catégorisation d'un code généré automatiquement.

Il existe d'autres sous-ensembles de MISRA C C:2023 définis par Polyspace, appelés objectifs de qualité logicielle (SQO) qui peuvent avoir un impact direct ou indirect sur la précision de vos résultats. Lorsque vous configurez le contrôle du code, vous pouvez sélectionner ces sous-ensembles. Consultez Software Quality Objective Subsets for MISRA Coding Standards

Si vous utilisez une version spécifique du langage C, telle que C11 ou C17/C18, spécifiez la version C pour bénéficier d’une vérification plus précise de l’infraction à la norme MISRA C:2023. Consultez Version de la norme C (-c-version).

Résultats Polyspace

développer tout

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

Rubriques

Support Polyspace pour MISRA C:2023

Sous-ensembles MISRA C:2023

Règles MISRA C:2023 spécifiques