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: 25 rules found
bad-practice
    Impact
      Clean code attribute
        1. Pointer and reference parameters should be "const" if the corresponding object is not modified

           Code Smell
        2. Reserved identifiers should not be defined or declared

           Code Smell
        3. Only standard forms of the "defined" directive should be used

           Code Smell
        4. Function-like macros should not be used

           Code Smell
        5. Recursion should not be used

           Code Smell
        6. "continue" should not be used

           Code Smell
        7. Bitwise operators should not be applied to signed operands

           Bug
        8. Functions should be declared explicitly

           Code Smell
        9. Names of well-known C standard library macros and functions should not be used as identifiers

           Code Smell
        10. Macros should not be used as replacements for "typedef" and "using"

           Code Smell
        11. Size of bit fields should not exceed the size of their types

           Code Smell
        12. Pointer and reference local variables should be "const" if the corresponding object is not modified

           Code Smell
        13. Argument of "printf" should be a format string

           Code Smell
        14. Loops with at most one iteration should be refactored

           Bug
        15. "if" statements should be preferred over "switch" when simpler

           Code Smell
        16. Track uses of "NOSONAR" comments

           Code Smell
        17. Deprecated attributes should include explanations

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

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

           Bug
        20. "Dynamic memory" should not be used

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

           Code Smell
        22. 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
        23. Functions shall not call themselves, either directly or indirectly

           Code Smell
        24. The target type of a pointer or "lvalue" reference parameter should be const-qualified appropriately

           Code Smell
        25. "Trigraph-like sequences" should not be used

           Code Smell

        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