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 798
  • Vulnerability14
  • Bug173
  • Security Hotspot19
  • Code Smell592

  • Quick Fix 99
Filtered: 35 rules found
unused
    Impact
      Clean code attribute
        1. Non-empty statements should change control flow or have at least one side-effect

           Bug
        2. Unused type declarations should be removed

           Code Smell
        3. Calls to "std::format" with a locale should use the "L" flag

           Code Smell
        4. "std::format" should not have unused arguments

           Code Smell
        5. "std::format" should not be missing indexes

           Bug
        6. Width, alignment, and padding format options should be used consistently

           Code Smell
        7. Functions that are not used in a project should be removed

           Code Smell
        8. "extern" shouldn't be used on member definitions

           Bug
        9. Reference types should not be qualified with "const" or "volatile"

           Code Smell
        10. Namespaces should not be empty

           Code Smell
        11. Forward declarations should not be redundant

           Code Smell
        12. Declarations should not be empty

           Code Smell
        13. "catch" clauses should do more than rethrow

           Code Smell
        14. Conditionally executed code should be reachable

           Bug
        15. Values should not be uselessly incremented

           Bug
        16. Related "if/else if" statements should not have the same condition

           Bug
        17. Unused assignments should be removed

           Code Smell
        18. All code should be reachable

           Bug
        19. Unused local variables should be removed

           Code Smell
        20. Sections of code should not be commented out

           Code Smell
        21. Unused function parameters should be removed

           Code Smell
        22. Unused functions and methods should be removed

           Code Smell
        23. Empty statements should be removed

           Code Smell
        24. Unused "private" fields should be removed

           Code Smell
        25. Unused labels should be removed

           Code Smell
        26. Condition-specific "catch" handlers should not be used after the ellipsis (catch-all) handler

           Bug
        27. Functions with "limited visibility" should be "used" at least once

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

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

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

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

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

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

           Code Smell
        34. Controlling expressions should not be invariant

           Bug
        35. A function shall not contain "unreachable" statements

           Bug

        A function shall not contain "unreachable" statements

        intentionality - logical
        reliability
        Bug
        Quick FixIDE quick fixes available with SonarQube for IDE
        • unused
        • cwe
        • 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 0.0.1 - A function shall not contain unreachable statements

        [IEC 61508-7] / C.5.9
        [DO-178C] / 6.4.4.3.c
        [ISO 26262-6] / 9.4

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Amplification

        A statement is unreachable if the block containing it is not reachable from the entry block of the Control Flow Graph (CFG) for the function.

        For the purpose of this rule:

        • Both operands of a reachable logical AND (&&) or logical OR (||) operator are considered reachable; and
        • All three operands of a reachable conditional operator (?:) are considered reachable; and
        • The blocks linked by the edges from a condition of a selection-statement or an iteration-statement are all considered reachable, except when the condition is a constant expression, in which case only the blocks linked by edges selected by the condition are considered reachable; and
        • A call to a function declared [[noreturn]] has no CFG out edge; and
        • If a try compound-statement of a (function-)try-block does not contain a reachable, potentially-throwing statement, then all catch-handlers are unreachable, otherwise all catch-handlers are considered reachable subject to the restriction that a catch-handler that appears after a more generic handler of the same try-block is not reachable.

        The rule does not apply to statements in the discarded branch of a constexpr if statement.

        Rationale

        Unreachable code often indicates a defect in the program, as, assuming that the program does not exhibit any undefined behaviour, unreachable code cannot be executed and cannot have any effect on the program’s outputs.

        In order to avoid crosstalk with M23_002: MISRA C++ 2023 Rule 0.0.2, the handling of logical and conditional operators in the conceptual CFG used by this rule differs from that in a traditional CFG.

        Example

        bool f0();
        
        int32_t f1( int32_t c, int32_t & res )
        {
          if ( false && f0() ) { }  // Compliant - statement is considered to be reachable
        
          return res;
        
          res = c;                  // Non-compliant - not reachable from entry block
        
          bool result;              // Non-compliant - not reachable from entry block
        }
        
        void f2( int32_t i )
        {
          while ( true )            // Constant condition - single edge into body of loop
          {
            if ( i != 0 )
            {
              break;                // Adds edge to statements following the loop body
            }
          }
        
          ++i;                      // Compliant - reachable via 'break'
        
          while ( true )            // Constant condition - single edge into body of loop
          {
            f();
          }
        
          ++i;                      // Non-compliant - not reachable from entry block
        }
        
        void f3( int32_t i )
        {
          goto LABEL;
          ++i;                      // Non-compliant - no edge to this block
        
        LABEL:
          ++i;                      // Compliant
        }
        
        class BaseException {};
        class DerivedException: public BaseException {};
        
        void f4()
        {
          try { /* ... */ }
          catch ( BaseException    & b ) { }
          catch ( DerivedException & d ) { }   // Non-compliant - will be caught above
        }
        
        void f5() noexcept;
        
        void f6()
        {
          try { f5(); }
          catch ( int32_t ) { }     // Non-compliant - f5 is not potentially-throwing
          catch ( ... )     { }     // Non-compliant - f5 is not potentially-throwing
        }
        
        void f7( int32_t i )
        {
          try
          {
            throw i;
            ++i;                    // Non-compliant - no edge to this block
          }
          catch ( int32_t ) { }     // Compliant - all catch-handlers are reachable
          catch ( int16_t ) { }     // Compliant - all catch-handlers are reachable
        
          ++i;                      // Compliant
        }
        
        void f8();
        
        int32_t f9( int32_t i )
        {
          try
          {
            f8();                   // Potentially-throwing
            return i * 2;           // Compliant
          }
          catch( int32_t ) { }      // Compliant - all catch-handlers are reachable
        
          return 0;                 // Compliant - even if f8 throws a type
        }                           //             other than int32_t
        
        [[noreturn]] void f10() noexcept;
        
        int32_t f11()
        {
          f10();                    // Does not return
          return 0;                 // Non-compliant
        }
        

        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