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: 30 rules found
misra-advisory
    Impact
      Clean code attribute
        1. Floating-point arithmetic should be used appropriately

           Bug
        2. The "goto" statement should not be used

           Code Smell
        3. The built-in unary "+" operator should not be used

           Code Smell
        4. Functions with "limited visibility" should be "used" at least once

           Code Smell
        5. All variables should be initialized

           Code Smell
        6. "Dynamic memory" should not be used

           Code Smell
        7. The "#pragma" directive and the "_Pragma" operator should not be used

           Code Smell
        8. The "#" and "##" preprocessor operators should not be used

           Code Smell
        9. Program-terminating functions should not be used

           Code Smell
        10. Bit-fields should not be declared

           Code Smell
        11. A "declaration" should not declare more than one variable or member variable

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

           Code Smell
        13. The result of an assignment operator should not be "used"

           Code Smell
        14. An unsigned arithmetic operation with constant operands should not wrap

           Bug
        15. The comma operator should not be used

           Code Smell
        16. The right-hand operand of a logical "&&" or "||" operator should not contain "persistent side effects"

           Bug
        17. The built-in unary "-" operator should not be applied to an expression of unsigned type

           Bug
        18. A cast should not convert a pointer type to an integral type

           Code Smell
        19. The "declaration" of an object should contain no more than two levels of pointer indirection

           Code Smell
        20. Parentheses should be used to make the meaning of an expression appropriately explicit

           Code Smell
        21. The names of the "standard signed integer types" and "standard unsigned integer types" should not be used

           Code Smell
        22. A function or object with external linkage should be "introduced" in a "header file"

           Code Smell
        23. "#undef" should only be used for macros defined previously in the same file

           Code Smell
        24. "#include" directives should only be preceded by preprocessor directives or comments

           Code Smell
        25. Sections of code should not be "commented out"

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

           Code Smell
        27. A value should not be "unnecessarily written" to a local object

           Code Smell
        28. Types with "limited visibility" should be "used" at least once

           Code Smell
        29. Variables with "limited visibility" should be "used" at least once

           Code Smell
        30. Controlling expressions should not be invariant

           Bug

        Variables with "limited visibility" should be "used" at least once

        intentionality - clear
        maintainability
        Code Smell
        • unused
        • misra-c++2023
        • misra-advisory

        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 0.2.1 - Variables with limited visibility should be used [1] at least once

        Category: Advisory

        Analysis: Decidable,Single Translation Unit

        Amplification

        A variable has limited visibility if it is not a function parameter, and it has internal linkage or no linkage.

        A variable is used [1] when:

        • It is part of an id-expression; or
        • The variable is of class type and has a user-provided constructor or a user-provided destructor.

        Rationale

        Variables that are declared and never used within a project do not contribute to program output; they constitute noise and may indicate that the wrong variable name has been used or that one or more statements are missing.

        Note: this rule allows the introduction of variables for the sole purpose of providing scoped resource allocation and release. For example:

        {
          std::lock_guard< std::mutex > lock { mutex };    // Compliant - has user-provided
                                                           //             constructor
          // ...
        } // User-provided destructor implicitly called here
        

        Exception

        This rule does not apply to:

        • Variables that have at least one declaration [2] with the [[maybe_unused]] attribute.
        • Constant variables at namespace scope that are declared within a header file [3].

        Example

        class C { };                  // No user-provided constructor or destructor
        
        namespace
        {
          C c;                        // Non-compliant - unused
        }
        
        void maybeUnused( int32_t a )
        {
          [[maybe_unused]]
            bool b = a > 0;           // Compliant (by exception #1 if NDEBUG is defined)
        
          assert( b );                // Does not use b if NDEBUG is defined
        
          usefn( a );
        }
        
        const int16_t x = 19;         // Compliant - x is read in initializedButNotUsed
        const int16_t y = 21;         // Non-compliant - would be compliant by exception #2
                                      //                 if declared in a header file
        
        void initializedButNotUsed()
        {
          int16_t local_1 = 42;       // Non-compliant - local_1 is never read
          int16_t local_2;            // Compliant
        
          local_2 = x;                // Use of local_2 for the purposes of this rule
        }
        
        void userProvidedCtor()
        {
          std::ifstream fs { "cfg.ini" };    // Compliant - user-provided constructor
        }
        

        Glossary

        [1] Use / used / using

        An object is used if:

        • It is the subject of a cast; or
        • It is explicitly initialized at declaration time; or
        • It is an operand in an expression; or
        • It is referenced.

        A function is used as defined in M23_331: MISRA C++ 2023 Rule 0.2.4.

        A type is used as defined in M23_005: MISRA C++ 2023 Rule 0.2.3.

        [2] Declaration

        A declaration introduces the name of an entity into a translation unit (see [basic.def]/1).

        An entity may be declared several times. The first declaration of an entity in a translation unit is called an introduction [4]. All subsequent declarations are called redeclarations [5].

        A definition [6] is a declaration, as described in [basic.def]/2.

        [3] Header file

        A header file is considered to be any file that is included during preprocessing (for example via the #include directive), regardless of its name or suffix.

        [4] Introduction

        See declaration [2].

        [5] Redeclaration

        See declaration [2].

        [6] Definition

        See declaration [2].

        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