SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code

  • All rules 420
  • Vulnerability14
  • Bug111
  • Security Hotspot19
  • Code Smell276

  • Quick Fix 27
Filtered: 69 rules found
misra-required
    Impact
      Clean code attribute
        1. A function call shall not violate the function's preconditions

           Bug
        2. An "integer-literal" of type "long long" shall not use a single "L" or "l" in any suffix

           Code Smell
        3. The literal value zero shall be the only value assigned to "errno"

           Code Smell
        4. There shall be no occurrence of "undefined" or "critical unspecified behaviour"

           Bug
        5. User-defined identifiers shall have an appropriate form

           Code Smell
        6. "Global variables" shall not be used

           Code Smell
        7. The "volatile" qualifier shall be used appropriately

           Bug
        8. "Integral promotion" and the "usual arithmetic conversions" shall not change the signedness or the "type category" of an operand

           Code Smell
        9. The operands of "bitwise operators" and "shift operators" shall be appropriate

           Bug
        10. The argument to a "mixed-use macro parameter" shall not be subject to further expansion

           Code Smell
        11. An "object pointer type" shall not be cast to an integral type other than "std::uintptr_t" or "std::intptr_t"

           Code Smell
        12. The library function "system" from "<cstdlib>" shall not be used

           Vulnerability
        13. Reads and writes on the same file stream shall be separated by a positioning operation

           Bug
        14. Line-splicing shall not be used in "//" comments

           Bug
        15. Octal escape sequences, hexadecimal escape sequences and universal character names shall be terminated

           Code Smell
        16. Dynamic memory shall be managed automatically

           Code Smell
        17. Local variables shall not have static storage duration

           Code Smell
        18. The facilities provided by the standard "header file" "<csignal>" shall not be used

           Code Smell
        19. The macro "offsetof" shall not be used

           Code Smell
        20. The standard "header file" "<csetjmp>" shall not be used

           Code Smell
        21. A macro parameter immediately following a "#" operator shall not be immediately followed by a "##" operator

           Code Smell
        22. The "#include" directive shall be followed by either a "<filename>" or ""filename"" sequence

           Bug
        23. The "'" or """ or "\" characters and the "/*" or "//" character sequences shall not occur in a "header file" name

           Bug
        24. Precautions shall be taken in order to prevent the contents of a "header file" being included more than once

           Code Smell
        25. 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

           Code Smell
        26. The "defined" preprocessor operator shall be used appropriately

           Bug
        27. A named bit-field with "signed integer type" shall not have a length of one bit

           Bug
        28. A bit-field shall have an appropriate type

           Code Smell
        29. Within an enumerator list, the value of an implicitly-specified "enumeration constant" shall be unique

           Code Smell
        30. A conversion from function type to pointer-to-function type shall only occur in appropriate contexts

           Code Smell
        31. A function with non-"void" return type shall return a value on all paths

           Bug
        32. The parameters in all "declarations" or overrides of a function shall either be unnamed or have identical names

           Code Smell
        33. The features of "<cstdarg>" shall not be used

           Code Smell
        34. Functions shall not call themselves, either directly or indirectly

           Code Smell
        35. An assignment operator shall not assign the address of an object with automatic storage duration to an object with a greater lifetime

           Code Smell
        36. The "asm" declaration shall not be used

           Code Smell
        37. The "goto" statement shall jump to a label declared later in the function body

           Code Smell
        38. A "goto" statement shall reference a label in a surrounding block

           Code Smell
        39. The structure of a "switch" statement shall be appropriate

           Code Smell
        40. All "if ... else if" constructs shall be terminated with an "else" statement

           Code Smell
        41. The body of an "iteration-statement" or a "selection-statement" shall be a "compound-statement"

           Code Smell
        42. An object with integral, enumerated, or pointer to "void" type shall not be cast to a pointer type

           Code Smell
        43. Casts shall not be performed between a pointer to function and any other type

           Bug
        44. A cast shall not remove any "const" or "volatile" qualification from the type accessed via a pointer or by reference

           Code Smell
        45. The built-in relational operators ">", ">=", "<" and "<=" shall not be applied to objects of pointer type, except where they point to elements of the same array

           Bug
        46. Subtraction between pointers shall only be applied to pointers that address elements of the same array

           Bug
        47. Pointer arithmetic shall not form an invalid pointer

           Bug
        48. Operations on a memory location shall be sequenced appropriately

           Bug
        49. The same type aliases shall be used in all "declarations" of the same "entity"

           Code Smell
        50. The source code used to implement an "entity" shall appear only once

           Bug
        51. The "one-definition rule" shall not be violated

           Bug
        52. All "declarations" of a variable or function shall have the same type

           Bug
        53. Block scope "declarations" shall not be "visually ambiguous"

           Code Smell
        54. A "header file" shall not contain definitions of functions or objects that are non-inline and have external linkage

           Code Smell
        55. A line whose first token is "#" shall be a valid preprocessing directive

           Bug
        56. All identifiers used in the controlling expression of "#if" or "#elif" preprocessing directives shall be defined prior to evaluation

           Bug
        57. Parentheses shall be used to ensure macro arguments are expanded appropriately

           Code Smell
        58. Tokens that look like a preprocessing directive shall not occur within a macro argument

           Bug
        59. Function-like macros shall not be defined

           Code Smell
        60. String literals with different encoding prefixes shall not be concatenated

           Bug
        61. The lowercase form of "L" shall not be used as the first character in a literal suffix

           Code Smell
        62. Unsigned "integer literals" shall be appropriately suffixed

           Code Smell
        63. Octal constants shall not be used

           Code Smell
        64. Within character literals and non raw-string literals, "\" shall only be used to form a defined escape sequence or universal character name

           Bug
        65. A variable declared in an "inner scope" shall not hide a variable declared in an "outer scope"

           Code Smell
        66. The character sequence "/*" shall not be used within a C-style comment

           Code Smell
        67. A named function parameter shall be "used" at least once

           Code Smell
        68. The value returned by a function shall be "used"

           Code Smell
        69. A function shall not contain "unreachable" statements

           Bug

        The operands of "bitwise operators" and "shift operators" shall be appropriate

        intentionality - logical
        reliability
        Bug
        • bad-practice
        • misra-c++2023
        • misra-required

        Why is this an issue?

        More Info

        This rule is part of MISRA C++:2023.

        Usage of this content is governed by Sonar’s terms and conditions. Redistribution is prohibited.

        Rule 7.0.4 - The operands of bitwise operators and shift operators shall be appropriate

        [expr.bit.and]
        [expr.or]
        [expr.xor]
        [expr.shift]

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Amplification

        The following shall be of an unsigned type:

        • Both operands of the binary bitwise operators;
        • The left operand of the shift operators;
        • The operand of the bit complement operator.

        The right operand of the shift operators, shall be:

        • Either a non-constant expression with an unsigned type; or
        • A constant expression with a value between 0 and sizeof( T ) * CHAR_BIT - 1 (inclusive), where T is the type of the left operand (before integral promotion).

        The requirements of this rule for binary bitwise operators also apply to the corresponding compound assignment forms.

        Rationale

        Bit-oriented operations may be applied to operands of signed and unsigned type. However, the result is only guaranteed to be defined when the sign bit is not affected.

        Unlike most other binary operations, the operands to the shift operators do not undergo the usual arithmetic conversions. Both operands are still subject to integral promotion, with the resulting type being the promoted type of the left operand. Explicitly casting the left-hand operand of the shift operator to the intended width allows the reader to reason about the code’s correctness without having to consider integral promotion.

        The following behaviours may occur if operands to a shift operator have a signed type:

        • Shifting by a negative value results in undefined behaviour;
        • A left-shift of a signed left operand can result in undefined behaviour, even when the value is positive;
        • Right-shifting a negative value results in an implementation-defined value.

        Additionally, undefined behaviour occurs when a shift operator has a right operand with a value that is greater than or equal to the size in bits of the promoted type of the left operand.

        Exception

        The left operand of a shift operator is permitted to be a non-negative constant expression of a signed type T (before integral promotion) when:

        • T uses two’s complement representation; and
        • The right operand is also a constant expression with a value between 0 and sizeof( T ) * CHAR_BIT - 1 (inclusive); and
        • No set bit is shifted into or beyond the most significant bit, which is used as the sign bit.

        Example

        The following examples assume int uses 32-bit two’s complement representation.

        1u << u8;                                  // Compliant
        1u << 31;                                  // Compliant
        1_u8 << 2;                                 // Compliant - but violates other rules
        u8 << 2;                                   // Compliant - but violates other rules
        
        s32 << 2;                                  // Non-compliant - left operand is signed
        1 << u8;                                   // Non-compliant - left operand is signed
        ( u8 + u16 ) << 2;                         // Non-compliant - result of + is signed
        static_cast< uint16_t >( u8 + u16 ) << 2;  // Compliant
        
        1LL << 31;                                 // Compliant by exception
        1 << 30;                                   // Compliant by exception
        2 << 30;                                   // Non-compliant - exception does not
                                                   //   apply as set bit is shifted too far
        
        u32a | u32b;                               // Compliant
        s32a | s32b;                               // Non-compliant - signed operands
        
        ~u32;                                      // Compliant
        ~u8;                                       // Compliant - but violates other rules
        ~s32;                                      // Non-compliant - signed operand
        

        Copyright The MISRA Consortium Limited © 2023

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use