Die Übersetzung dieser Seite ist veraltet. Klicken Sie hier, um die neueste Version auf Englisch zu sehen.

MISRA C:2023-Richtlinien und -Regeln

Liste und Beschreibung der MISRA™ C:2023-Richtlinien und -Regeln, die von Polyspace® unterstützt werden

Polyspace kann Ihren Code anhand der MISRA C™:2023-Codierungsregeln und -richtlinien überprüfen. Der MISRA C:2023-Standard konsolidiert folgende Anleitungen:

  • MISRA C:2012-Regeln und -Richtlinien.

  • Klarstellungen im technischen Korrigendum 1 (TC1) und im technischen Korrigendum 2 (TC2) hinzugefügt.

  • Neue Regeln und Abänderungen als Änderung 1 (AMD1), Änderung 2 (AMD2), Änderung 3 (AMD3) und Änderung 4 (AMD4) hinzugefügt.

Jede Anleitung wird einer der folgenden Kategorien zugeteilt: obligatorisch, erforderlich oder beratend. Wenn Sie die Regelprüfung einrichten, können Sie Untergruppen dieser Kategorien zur Prüfung auswählen. Verwenden Sie die Analyseoption Check MISRA C:2023 (-misra-c-2023), um Untergruppen der Regeln zu aktivieren.

Bei automatisch generiertem Code werden einige Regeln anderen Kategorien zugeteilt, einschließlich einer zusätzlichen Kategorie: Lesbarkeit. Mit der Option Use generated code requirements (-misra-c-2023-agc-mode) aktivieren Sie die Kategorisierung für automatisch generierten Code.

Es gibt zusätzliche Untergruppen der MISRA C:2023-Anleitungen, die von Polyspace definiert werden, und zwar die sogenannten Software-Qualitätsziele (SQO), die sich direkt oder indirekt auf die Genauigkeit Ihrer Ergebnisse auswirken können. Wenn Sie die Code-Überprüfung einrichten, können Sie diese Untergruppen auswählen. Siehe Software Quality Objective Subsets for MISRA Coding Standards.

Wenn Sie eine bestimmte Version der C-Sprache verwenden, wie z. B. C11 oder C17/C18, geben Sie die C-Version an, um eine genauere Prüfung auf Verstöße gegen MISRA C:2023 zu ermöglichen. Siehe C standard version (-c-version).

Polyspace-Ergebnisse

alle erweitern

MISRA C:2023 Dir 1.1Any implementation-defined behavior on which the output of the program depends shall be documented and understood (Seit R2024a)
MISRA C:2023 Dir 2.1All source files shall compile without any compilation errors (Seit R2024a)
MISRA C:2023 Dir 4.1Run-time failures shall be minimized (Seit R2024a)
MISRA C:2023 Dir 4.3Assembly language shall be encapsulated and isolated (Seit R2024a)
MISRA C:2023 Dir 4.4Sections of code should not be "commented out" (Seit R2024a)
MISRA C:2023 Dir 4.5Identifiers in the same name space with overlapping visibility should be typographically unambiguous (Seit R2024a)
MISRA C:2023 Dir 4.6 typedefs that indicate size and signedness should be used in place of the basic numerical types (Seit R2024a)
MISRA C:2023 Dir 4.7If a function returns error information, then that error information shall be tested (Seit 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 (Seit R2024a)
MISRA C:2023 Dir 4.9A function should be used in preference to a function-like macro where they are interchangeable (Seit R2024a)
MISRA C:2023 Dir4.10Precautions shall be taken in order to prevent the contents of a header file being included more than once (Seit R2024a)
MISRA C:2023 Dir4.11The validity of values passed to library functions shall be checked (Seit R2024a)
MISRA C:2023 Dir4.12Dynamic memory allocation shall not be used (Seit R2024a)
MISRA C:2023 Dir4.13Functions which are designed to provide operations on a resource should be called in an appropriate sequence (Seit R2024a)
MISRA C:2023 Dir4.14The validity of values received from external sources shall be checked (Seit R2024a)
MISRA C:2023 Dir4.15Evaluation of floating-point expressions shall not lead to the undetected generation of infinities and NaNs (Seit R2024a)
MISRA C:2023 Dir5.1There shall be no data races between threads (Seit R2024b)
MISRA C:2023 Dir5.2There shall be no deadlocks between threads (Seit R2024b)
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 (Seit R2024a)
MISRA C:2023 Rule 1.2Language extensions should not be used (Seit R2024a)
MISRA C:2023 Rule 1.3There shall be no occurrence of undefined or critical unspecified behaviour (Seit R2024a)
MISRA C:2023 Rule 1.4Emergent language features shall not be used (Seit R2024a)
MISRA C:2023 Rule 1.5Obsolescent language features shall not be used (Seit R2024a)
MISRA C:2023 Rule2.1A project shall not contain unreachable code (Seit R2024a)
MISRA C:2023 Rule2.2A project shall not contain dead code (Seit R2024a)
MISRA C:2023 Rule2.3A project should not contain unused type declarations (Seit R2024a)
MISRA C:2023 Rule2.4A project should not contain unused tag declarations (Seit R2024a)
MISRA C:2023 Rule2.5A project should not contain unused macro definitions (Seit R2024a)
MISRA C:2023 Rule2.6A function should not contain unused label declarations (Seit R2024a)
MISRA C:2023 Rule2.7A function should not contain unused parameters (Seit R2024a)
MISRA C:2023 Rule2.8A project should not contain unused object definitions (Seit R2024b)
MISRA C:2023 Rule 3.1The character sequences /* and // shall not be used within a comment (Seit R2024a)
MISRA C:2023 Rule 3.2Line-splicing shall not be used in // comments (Seit R2024a)
MISRA C:2023 Rule 4.1Octal and hexadecimal escape sequences shall be terminated (Seit R2024a)
MISRA C:2023 Rule 4.2Trigraphs should not be used (Seit R2024a)
MISRA C:2023 Rule 5.1External identifiers shall be distinct (Seit R2024a)
MISRA C:2023 Rule 5.2Identifiers declared in the same scope and name space shall be distinct (Seit R2024a)
MISRA C:2023 Rule 5.3An identifier declared in an inner scope shall not hide an identifier declared in an outer scope (Seit R2024a)
MISRA C:2023 Rule 5.4Macro identifiers shall be distinct (Seit R2024a)
MISRA C:2023 Rule 5.5Identifiers shall be distinct from macro names (Seit R2024a)
MISRA C:2023 Rule 5.6A typedef name shall be a unique identifier (Seit R2024a)
MISRA C:2023 Rule 5.7A tag name shall be a unique identifier (Seit R2024a)
MISRA C:2023 Rule 5.8Identifiers that define objects or functions with external linkage shall be unique (Seit R2024a)
MISRA C:2023 Rule 5.9Identifiers that define objects or functions with internal linkage should be unique (Seit R2024a)
MISRA C:2023 Rule 6.1Bit-fields shall only be declared with an appropriate type (Seit R2024a)
MISRA C:2023 Rule 6.2Single-bit named bit-fields shall not be of a signed type (Seit R2024a)
MISRA C:2023 Rule 6.3A bit field shall not be declared as a member of a union (Seit R2024a)
MISRA C:2023 Rule7.1Octal constants shall not be used (Seit R2024a)
MISRA C:2023 Rule7.2A “u” or “U” suffix shall be applied to all integer constants that are represented in an unsigned type (Seit R2024a)
MISRA C:2023 Rule7.3The lowercase character “l” shall not be used in a literal suffix (Seit R2024a)
MISRA C:2023 Rule7.4A string literal shall not be assigned to an object unless the object’s type is “pointer to const-qualified char” (Seit R2024a)
MISRA C:2023 Rule7.5The argument of an integer constant macro shall have an appropriate form (Seit R2024a)
MISRA C:2023 Rule7.6The small integer variants of the minimum-width integer constant macros shall not be used (Seit R2025a)
MISRA C:2023 Rule 8.1Types shall be explicitly specified (Seit R2024a)
MISRA C:2023 Rule 8.2Function types shall be in prototype form with named parameters (Seit R2024a)
MISRA C:2023 Rule 8.3All declarations of an object or function shall use the same names and type qualifiers (Seit R2024a)
MISRA C:2023 Rule 8.4A compatible declaration shall be visible when an object or function with external linkage is defined (Seit R2024a)
MISRA C:2023 Rule 8.5An external object or function shall be declared once in one and only one file (Seit R2024a)
MISRA C:2023 Rule 8.6An identifier with external linkage shall have exactly one external definition (Seit 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 (Seit 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 (Seit R2024a)
MISRA C:2023 Rule 8.9An object should be declared at block scope if its identifier only appears in a single function (Seit R2024a)
MISRA C:2023 Rule8.10An inline function shall be declared with the static storage class (Seit R2024a)
MISRA C:2023 Rule8.11When an array with external linkage is declared, its size should be explicitly specified (Seit R2024a)
MISRA C:2023 Rule8.12Within an enumerator list, the value of an implicitly-specified enumeration constant shall be unique (Seit R2024a)
MISRA C:2023 Rule8.13A pointer should point to a const-qualified type whenever possible (Seit R2024a)
MISRA C:2023 Rule8.14The restrict type qualifier shall not be used (Seit R2024a)
MISRA C:2023 Rule8.15The argument of an integer constant macro shall have an appropriate form (Seit R2024a)
MISRA C:2023 Rule8.16The alignment specification of zero should not appear in an object declaration (Seit R2024a)
MISRA C:2023 Rule8.17At most one explicit alignment specifier should appear in an object declaration (Seit R2024a)
MISRA C:2023 Rule9.1The value of an object with automatic storage duration shall not be read before it has been set (Seit R2024a)
MISRA C:2023 Rule9.2The initializer for an aggregate or union shall be enclosed in braces (Seit R2024a)
MISRA C:2023 Rule9.3Arrays shall not be partially initialized (Seit R2024a)
MISRA C:2023 Rule9.4An element of an object shall not be initialized more than once (Seit R2024a)
MISRA C:2023 Rule9.5Where designated initializers are used to initialize an array object the size of the array shall be specified explicitly (Seit R2024a)
MISRA C:2023 Rule9.6An initializer using chained designators shall not contain initializers without designators (Seit R2025a)
MISRA C:2023 Rule 10.1Operands shall not be of an inappropriate essential type (Seit R2024a)
MISRA C:2023 Rule 10.2Expressions of essentially character type shall not be used inappropriately in addition and subtraction operations (Seit 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 (Seit 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 (Seit R2024a)
MISRA C:2023 Rule 10.5The value of an expression should not be cast to an inappropriate essential type (Seit R2024a)
MISRA C:2023 Rule 10.6The value of a composite expression shall not be assigned to an object with wider essential type (Seit 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 (Seit 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 (Seit R2024a)
MISRA C:2023 Rule11.1Conversions shall not be performed between a pointer to a function and any other type (Seit R2024a)
MISRA C:2023 Rule11.2Conversions shall not be performed between a pointer to an incomplete type and any other type (Seit R2024a)
MISRA C:2023 Rule11.3A conversion shall not be performed between a pointer to object type and a pointer to a different object type (Seit R2024a)
MISRA C:2023 Rule11.4A conversion should not be performed between a pointer to object and an integer type (Seit R2024a)
MISRA C:2023 Rule11.5A conversion should not be performed from pointer to void into pointer to object (Seit R2024a)
MISRA C:2023 Rule11.6A cast shall not be performed between pointer to void and an arithmetic type (Seit R2024a)
MISRA C:2023 Rule11.7A cast shall not be performed between pointer to object and a non-integer arithmetic type (Seit R2024a)
MISRA C:2023 Rule11.8A conversion shall not remove any const, volatile, or _Atomic qualification from the type pointed to by a pointer (Seit R2024a)
MISRA C:2023 Rule11.9The macro NULL shall be the only permitted form of integer null pointer constant (Seit R2024a)
MISRA C:2023 Rule11.10The _Atomic qualifier shall not be applied to the incomplete type void (Seit R2024b)
MISRA C:2023 Rule12.1The precedence of operators within expressions should be made explicit (Seit R2024a)
MISRA C:2023 Rule12.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 (Seit R2024a)
MISRA C:2023 Rule12.3The comma operator should not be used (Seit R2024a)
MISRA C:2023 Rule12.4Evaluation of constant expressions should not lead to unsigned integer wrap-around (Seit R2024a)
MISRA C:2023 Rule12.5The sizeof operator shall not have an operand which is a function parameter declared as “array of type” (Seit R2024a)
MISRA C:2023 Rule12.6Structure and union members of atomic objects shall not be directly accessed (Seit R2025a)
MISRA C:2023 Rule 13.1Initializer lists shall not contain persistent side effects (Seit 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 (Seit 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 (Seit R2024a)
MISRA C:2023 Rule 13.4The result of an assignment operator should not be used (Seit R2024a)
MISRA C:2023 Rule 13.5The right hand operand of a logical && or || operator shall not contain persistent side effects (Seit R2024a)
MISRA C:2023 Rule 13.6The operand of the sizeof operator shall not contain any expression which has potential side effects (Seit R2024a)
MISRA C:2023 Rule 14.1A loop counter shall not have essentially floating type (Seit R2024a)
MISRA C:2023 Rule 14.2A for loop shall be well-formed (Seit R2024a)
MISRA C:2023 Rule 14.3Controlling expressions shall not be invariant (Seit 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 (Seit R2024a)
MISRA C:2023 Rule 15.1The goto statement should not be used (Seit R2024a)
MISRA C:2023 Rule 15.2The goto statement shall jump to a label declared later in the same function (Seit 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 (Seit R2024a)
MISRA C:2023 Rule 15.4There should be no more than one break or goto statement used to terminate any iteration statement (Seit R2024a)
MISRA C:2023 Rule 15.5A function should have a single point of exit at the end (Seit R2024a)
MISRA C:2023 Rule 15.6The body of an iteration-statement or a selection-statement shall be a compound statement (Seit R2024a)
MISRA C:2023 Rule 15.7All if … else if constructs shall be terminated with an else statement (Seit R2024a)
MISRA C:2023 Rule 16.1All switch statements shall be well-formed (Seit 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 (Seit R2024a)
MISRA C:2023 Rule 16.3An unconditional break statement shall terminate every switch-clause (Seit R2024a)
MISRA C:2023 Rule 16.4Every switch statement shall have a default label (Seit R2024a)
MISRA C:2023 Rule 16.5A default label shall appear as either the first or the last switch label of a switch statement (Seit R2024a)
MISRA C:2023 Rule 16.6Every switch statement shall have at least two switch-clauses (Seit R2024a)
MISRA C:2023 Rule 16.7A switch-expression shall not have essentially Boolean type (Seit R2024a)
MISRA C:2023 Rule 17.1The standard header file <stdarg.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule 17.2Functions shall not call themselves, either directly or indirectly (Seit R2024a)
MISRA C:2023 Rule 17.3A function shall not be declared implicitly (Seit 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 (Seit 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 (Seit R2024a)
MISRA C:2023 Rule 17.6The declaration of an array parameter shall not contain the static keyword between the [ ] (Seit R2024a)
MISRA C:2023 Rule 17.7The value returned by a function having non-void return type shall be used (Seit R2024a)
MISRA C:2023 Rule 17.8A function parameter should not be modified (Seit R2024a)
MISRA C:2023 Rule 17.9A function declared with a _Noreturn function specifier shall not return to its caller (Seit R2024a)
MISRA C:2023 Rule17.10A function declared with a _Noreturn function specifier shall have void return type (Seit R2024a)
MISRA C:2023 Rule17.11A function that never returns should be declared with a _Noreturn function specifier (Seit R2024a)
MISRA C:2023 Rule17.12A function identifier should only be used with either a preceding &, or with a parenthesized parameter list (Seit R2024a)
MISRA C:2023 Rule17.13A function type shall not be type qualified (Seit R2024a)
MISRA C:2023 Rule18.1A pointer resulting from arithmetic on a pointer operand shall address an element of the same array as that pointer operand (Seit R2024a)
MISRA C:2023 Rule18.2Subtraction between pointers shall only be applied to pointers that address elements of the same array (Seit R2024a)
MISRA C:2023 Rule18.3The relational operators >, >=, < and <= shall not be applied to expressions of pointer type except where they point into the same object (Seit R2024a)
MISRA C:2023 Rule18.4The +, -, += and -= operators should not be applied to an expression of pointer type (Seit R2024a)
MISRA C:2023 Rule18.5Declarations should contain no more than two levels of pointer nesting (Seit R2024a)
MISRA C:2023 Rule18.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 (Seit R2024a)
MISRA C:2023 Rule18.7Flexible array members shall not be declared (Seit R2024a)
MISRA C:2023 Rule18.8Variable-length arrays shall not be used (Seit R2024a)
MISRA C:2023 Rule18.9An object with temporary lifetime shall not undergo array-to-pointer conversion (Seit R2024a)
MISRA C:2023 Rule18.10Pointers to variably-modified array types shall not be used (Seit R2025a)
MISRA C:2023 Rule 19.1An object shall not be assigned or copied to an overlapping object (Seit R2024a)
MISRA C:2023 Rule 19.2The union keyword should not be used (Seit R2024a)
MISRA C:2023 Rule 20.1#include directives should only be preceded by preprocessor directives or comments (Seit R2024a)
MISRA C:2023 Rule 20.2The ', " or \ characters and the /* or // character sequences shall not occur in a header file name (Seit R2024a)
MISRA C:2023 Rule 20.3The #include directive shall be followed by either a <filename> or "filename" sequence (Seit R2024a)
MISRA C:2023 Rule 20.4A macro shall not be defined with the same name as a keyword (Seit R2024a)
MISRA C:2023 Rule 20.5#undef should not be used (Seit R2024a)
MISRA C:2023 Rule 20.6Tokens that look like a preprocessing directive shall not occur within a macro argument (Seit R2024a)
MISRA C:2023 Rule 20.7Expressions resulting from the expansion of macro parameters shall be enclosed in parentheses (Seit R2024a)
MISRA C:2023 Rule 20.8The controlling expression of a #if or #elif preprocessing directive shall evaluate to 0 or 1 (Seit 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 (Seit R2024a)
MISRA C:2023 Rule20.10The # and ## preprocessor operators should not be used (Seit R2024a)
MISRA C:2023 Rule20.11A macro parameter immediately following a # operator shall not immediately be followed by a ## operator (Seit R2024a)
MISRA C:2023 Rule20.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 (Seit R2024a)
MISRA C:2023 Rule20.13A line whose first token is # shall be a valid preprocessing directive (Seit R2024a)
MISRA C:2023 Rule20.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 (Seit R2024a)
MISRA C:2023 Rule21.1#define and #undef shall not be used on a reserved identifier or reserved macro name (Seit R2024a)
MISRA C:2023 Rule21.2A reserved identifier or reserved macro name shall not be declared (Seit R2024a)
MISRA C:2023 Rule21.3The memory allocation and deallocation functions of <stdlib.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.4The standard header file <setjmp.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.5The standard header file <signal.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.6The Standard Library input/output functions shall not be used (Seit R2024a)
MISRA C:2023 Rule21.7The Standard Library functions atof, atoi, atol, and atoll functions of <stdlib.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.8The Standard Library termination functions of <stdlib.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.9The Standard Library library functions bsearch and qsort of <stdlib.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.10The Standard Library time and date functions shall not be used (Seit R2024a)
MISRA C:2023 Rule21.11The standard header file <tgmath.h> should not be used (Seit R2024a)
MISRA C:2023 Rule21.12The standard header file <fenv.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.13Any value passed to a function in <ctype.h> shall be representable as an unsigned char or be the value EOF (Seit R2024a)
MISRA C:2023 Rule21.14The Standard Library function memcmp shall not be used to compare null terminated strings (Seit R2024a)
MISRA C:2023 Rule21.15The pointer arguments to the Standard Library functions memcpy, memmove and memcmp shall be pointers to qualified or unqualified versions of compatible types (Seit R2024a)
MISRA C:2023 Rule21.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 (Seit R2024a)
MISRA C:2023 Rule21.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 (Seit R2024a)
MISRA C:2023 Rule21.18The size_t argument passed to any function in <string.h> shall have an appropriate value (Seit R2024a)
MISRA C:2023 Rule21.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 (Seit R2024a)
MISRA C:2023 Rule21.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 (Seit R2024a)
MISRA C:2023 Rule21.21The Standard Library function system of <stdlib.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.22All operand arguments to any type-generic macros declared in <tgmath.h> shall have an appropriate essential type (Seit R2024a)
MISRA C:2023 Rule21.23All operand arguments to any multi-argument type-generic macros declared in <tgmath.h> shall have the same standard type (Seit R2024a)
MISRA C:2023 Rule21.24The random number generator functions of <stdlib.h> shall not be used (Seit R2024a)
MISRA C:2023 Rule21.25All memory synchronization operations shall be executed in sequentially consistent order (Seit R2025a)
MISRA C:2023 Rule22.1All resources obtained dynamically by means of Standard Library functions shall be explicitly released (Seit R2024a)
MISRA C:2023 Rule22.2A block of memory shall only be freed if it was allocated by means of a Standard Library function (Seit R2024a)
MISRA C:2023 Rule22.3The same file shall not be open for read and write access at the same time on different streams (Seit R2024a)
MISRA C:2023 Rule22.4There shall be no attempt to write to a stream which has been opened as read-only (Seit R2024a)
MISRA C:2023 Rule22.5A pointer to a FILE object shall not be dereferenced (Seit R2024a)
MISRA C:2023 Rule22.6The value of a pointer to a FILE shall not be used after the associated stream has been closed (Seit R2024a)
MISRA C:2023 Rule22.7The macro EOF shall only be compared with the unmodified return value from any Standard Library function capable of returning EOF (Seit R2024a)
MISRA C:2023 Rule22.8The value of errno shall be set to zero prior to a call to an errno-setting-function (Seit R2024a)
MISRA C:2023 Rule22.9The value of errno shall be tested against zero after calling an errno-setting function (Seit R2024a)
MISRA C:2023 Rule22.10The value of errno shall only be tested when the last function to be called was an errno-setting function (Seit R2024a)
MISRA C:2023 Rule22.11A thread that was previously either joined or detached shall not be subsequently joined nor detached (Seit R2024b)
MISRA C:2023 Rule22.13Thread objects, thread synchronization objects and thread-specific storage pointers shall have appropriate storage duration (Seit R2025a)
MISRA C:2023 Rule22.15Thread synchronization objects and thread-specific storage pointers shall not be destroyed until after all threads accessing them have terminated (Seit R2024b)
MISRA C:2023 Rule22.16All mutex objects locked by a thread shall be explicitly unlocked by the same thread (Seit R2024b)
MISRA C:2023 Rule22.17No thread shall unlock a mutex or call cnd_wait() or cnd_timedwait() for a mutex it has not locked before (Seit R2024b)
MISRA C:2023 Rule22.18Non-recursive mutexes shall not be recursively locked (Seit R2025a)
MISRA C:2023 Rule23.1A generic selection should only be expanded from a macro (Seit R2024a)
MISRA C:2023 Rule23.2A generic selection that is not expanded from a macro shall not contain potential side effects in the controlling expression (Seit R2024a)
MISRA C:2023 Rule23.3A generic selection should contain at least one non-default association (Seit R2024a)
MISRA C:2023 Rule23.4A generic association shall list an appropriate type (Seit R2024a)
MISRA C:2023 Rule23.5A generic selection should not depend on implicit pointer type conversion (Seit R2024a)
MISRA C:2023 Rule23.6The controlling expression of a generic selection shall have an essential type that matches its standard type (Seit R2024a)
MISRA C:2023 Rule23.7A generic selection that is expanded from a macro should evaluate its argument only once (Seit R2024a)
MISRA C:2023 Rule23.8A default association shall appear as either the first or the last association of a generic selection (Seit R2024a)

Themen

Polyspace-Unterstützung für MISRA C:2023

MISRA C:2023-Untergruppen

Spezifische MISRA C:2023-Regeln