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

           Code Smell
        2. Non-standard characters should not occur in header file names in "#include" directives

           Bug
        3. Functions should not be declared at block scope

           Code Smell
        4. Literal suffix "L" for long integers shall be upper case

           Code Smell
        5. Digraphs should not be used

           Code Smell
        6. The first element of an array should not be accessed implicitly

           Code Smell
        7. A single L in a literal suffix should only be used for long values

           Code Smell
        8. Loop variables should be declared in the minimal possible scope

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

           Code Smell
        10. "sizeof" should not be called on pointers

           Bug
        11. Control characters should not be used in literals

           Code Smell
        12. Parameters should be passed in the correct order

           Code Smell
        13. Redundant casts should not be used

           Code Smell
        14. Multiple variables should not be declared on the same line

           Code Smell
        15. Unused local variables should be removed

           Code Smell
        16. Octal values should not be used

           Code Smell
        17. A "while" loop should be used instead of a "for" loop

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

           Code Smell
        19. Redundant pairs of parentheses should be removed

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

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

           Bug
        22. A "declaration" should not declare more than one variable or member variable

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

           Code Smell
        24. The lowercase form of "L" shall not be used as the first character in a literal suffix

           Code Smell
        25. Octal constants shall not be used

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

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

           Bug

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

        intentionality - clear
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarQube for IDE
        • 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 5.13.6 - An integer-literal of type long long shall not use a single L or l in any suffix

        [lex.icon]

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Amplification

        This rule applies to both signed long long and unsigned long long literals.

        Note: this rule does not apply to user-defined-literals.

        Rationale

        A literal with a suffix that has a single L could be a signed or unsigned long long. Use of the LL suffix for long long literals is more explicit and less error-prone.

        Example

        All of the following examples assume that long is 32-bits and long long is 64-bits.

        auto k1 = 12345678998L;        // Non-compliant
        auto k2 = 12345678998UL;       // Non-compliant
        auto k3 = 12345678998ull;      // Compliant
        auto k4 = 0xfeeddeadbeefL;     // Non-compliant
        auto k5 = 0xfeeddeadbeefLL;    // Compliant
        

        The rule does not apply to the following as the value is not long long:

        auto k6 = 12345L;
        auto k7 = 12345UL;
        auto k8 = 0x0badc0deL;
        

        The rule does not apply to the following as they do not have L or l suffixes:

        auto k9 = 12345678998;
        auto kA = 12345678998U;
        

        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