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: 27 rules found
brain-overload
    Impact
      Clean code attribute
        1. The global namespace should only contain "main", namespace declarations, and "extern" C declarations

           Code Smell
        2. "#undef" should be used with caution

           Code Smell
        3. Object declarations should contain no more than 2 levels of pointer indirection

           Code Smell
        4. "goto" statement should not be used

           Code Smell
        5. "[[nodiscard]]" attributes on types should include explanations

           Code Smell
        6. Cognitive Complexity of coroutines should not be too high

           Code Smell
        7. Cyclomatic Complexity of coroutines should not be too high

           Code Smell
        8. Coroutines should not have too many lines of code

           Code Smell
        9. "std::scoped_lock" should be used instead of "std::lock_guard"

           Code Smell
        10. Cognitive Complexity of functions should not be too high

           Code Smell
        11. "goto" statements should not be used to jump into blocks

           Code Smell
        12. Structures should not have too many fields

           Code Smell
        13. The ternary operator should not be used

           Code Smell
        14. Cyclomatic Complexity of functions should not be too high

           Code Smell
        15. "switch" statements should not have too many "case" clauses

           Code Smell
        16. Classes should not have too many methods

           Code Smell
        17. Functions/methods should not have too many lines

           Code Smell
        18. Control flow statements "if", "for", "while", "switch" and "try" should not be nested too deeply

           Code Smell
        19. "switch case" clauses should not have too many lines of code

           Code Smell
        20. Functions should not contain too many return statements

           Code Smell
        21. Magic numbers should not be used

           Code Smell
        22. Functions should not have too many parameters

           Code Smell
        23. Expressions should not be too complex

           Code Smell
        24. Files should not have too many lines of code

           Code Smell
        25. A function should have a single point of exit at the end of the function

           Code Smell
        26. "Legacy for statements" should be "simple"

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

           Code Smell

        A "goto" statement shall reference a label in a surrounding block

        intentionality - clear
        maintainability
        Code Smell
        • brain-overload
        • pitfall
        • 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 9.6.2 - A goto statement shall reference a label in a surrounding block

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Amplification

        A goto statement shall be enclosed in a statement that directly encloses [1] its referenced label.

        Rationale

        The unconstrained use of goto can lead to programs that are extremely difficult to comprehend and analyse. However, flags may need to be introduced to give the required control flow when it is not used, with the possibility that the flags may themselves make the code less transparent than if goto were used. The restricted use of goto is therefore allowed where that use will not lead to semantics contrary to developer expectations.

        This rule prohibits jumping in to nested blocks, as this results in complex control flow.

        Example

        void f1()
        {
          int32_t j = 0;
        
          goto L1;                                // Non-compliant
        
          for ( j = 0; j < 10 ; ++j )
          {
          L1:
            j;
          }
        }
        
        void f2()
        {
          for ( int32_t j = 0; j < 10 ; ++j )
          {
            for ( int32_t i = 0; i < 10; ++i )
            {
              goto L2;                            // Compliant
            }
          }
        
        L2:
          f1();
        }
        
        switch ( i )
        {
          case 0:
            if ( x < y )
              goto L3;                            // Non-compliant
            break;
        
          case 1:
          L3:
            break;
        }
        

        Glossary

        [1] Directly enclose

        See enclose [2].

        [2] Enclose

        A statement S1 directly encloses [1] a statement S2 if:

        • S1 is a labeled-statement, and S2 is the contained statement; or
        • S1 is a compound-statement, and S2 is any statement of its statement-seq; or
        • S1 is a selection-statement, and S2 is any of its statements (but not its init-statement); or
        • S1 is an iteration-statement, and S2 is the contained statement (but not an init-statement).

        A statement S1 encloses a statement S2 if:

        • S1 directly encloses [1] S2; or
        • S1 directly encloses [1] a statement S3 and S3 encloses S2.

        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