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: 45 rules found
suspicious
    Impact
      Clean code attribute
        1. "offsetof" macro should not be used

           Code Smell
        2. "errno" should not be used

           Code Smell
        3. Function names should be used either as a call with a parameter list or with the "&" operator

           Code Smell
        4. "enum" values should not be used as operands to built-in operators other than [ ], =, ==, !=, unary &, and the relational operators <, <=, >, >=

           Code Smell
        5. "bool" expressions should not be used as operands to built-in operators other than =, &&, ||, !, ==, !=, unary &, and the conditional operator

           Code Smell
        6. A cast shall not remove any const or volatile qualification from the type of a pointer or reference

           Code Smell
        7. Trigraphs should not be used

           Code Smell
        8. "#pragma pack" should be used correctly

           Bug
        9. Only valid arguments should be passed to UNIX/POSIX functions

           Code Smell
        10. Only valid arguments should be passed to stream functions

           Code Smell
        11. "^" should not be confused with exponentiation

           Code Smell
        12. Size of variable length arrays should be greater than zero

           Code Smell
        13. "mktemp" family of functions templates should have at least six trailing "X"s

           Code Smell
        14. Unevaluated operands should not have side effects

           Code Smell
        15. Size argument of memory functions should be consistent

           Code Smell
        16. Return value of "nodiscard" functions should not be ignored

           Code Smell
        17. Implicit casts should not lower precision

           Code Smell
        18. Appropriate size arguments should be passed to "strncat" and "strlcpy"

           Code Smell
        19. User-defined types should not be passed as variadic arguments

           Bug
        20. Array values should not be replaced unconditionally

           Bug
        21. A conditionally executed single line should be denoted by indentation

           Code Smell
        22. Conditionals should start on new lines

           Code Smell
        23. "case" ranges should cover multiple values

           Code Smell
        24. "switch" statements should cover all cases

           Code Smell
        25. Redundant pointer operator sequences should be removed

           Code Smell
        26. Conditionally executed code should be reachable

           Bug
        27. Flexible array members should not be declared

           Code Smell
        28. Track parsing failures

           Code Smell
        29. Recursion should not be infinite

           Bug
        30. Two branches in a conditional structure should not have exactly the same implementation

           Code Smell
        31. Pre-defined macros should not be defined, redefined or undefined

           Code Smell
        32. Switch cases should end with an unconditional "break" statement

           Code Smell
        33. "switch" statements should not contain non-case labels

           Code Smell
        34. Methods should not be empty

           Code Smell
        35. Assignments should not be made from within conditions

           Code Smell
        36. Variables should not be shadowed

           Code Smell
        37. Nested blocks of code should not be left empty

           Code Smell
        38. Within an enumerator list, the value of an implicitly-specified "enumeration constant" shall be unique

           Code Smell
        39. A conversion from function type to pointer-to-function type shall only occur in appropriate contexts

           Code Smell
        40. An assignment operator shall not assign the address of an object with automatic storage duration to an object with a greater lifetime

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

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

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

           Bug
        44. A cast shall not remove any "const" or "volatile" qualification from the type accessed via a pointer or by reference

           Code Smell
        45. All "declarations" of a variable or function shall have the same type

           Bug

        Within an enumerator list, the value of an implicitly-specified "enumeration constant" shall be unique

        intentionality - clear
        maintainability
        Code Smell
        • suspicious
        • 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 11.6.3 - Within an enumerator list, the value of an implicitly-specified enumeration constant shall be unique

        Category: Required

        Analysis: Decidable,Single Translation Unit

        Rationale

        An implicitly-specified enumeration constant has a value one greater than its predecessor. If the first enumeration constant is implicitly-specified, then its value is zero.

        An explicitly-specified enumeration constant has the value of the associated constant expression.

        If implicitly-specified and explicitly-specified constants are mixed within an enumeration list, it is possible for values to be duplicated. Such duplication may be unintentional and may give rise to unexpected behaviour.

        This rule requires that any duplication of enumeration constants be made explicit, thus making the intent clear.

        Exception

        An implicitly-specified enumeration constant may have the same value as an explicitly-specified enumeration constant from the same enumeration when the explicitly-specified value is defined using only the name of another enumeration constant.

        Example

        The following examples are compliant as it is clear which enumeration constants have the same value:

        enum E1 { A = 3, B, C = 5, D = 5 };           // Compliant
        enum E2 { A = 3, B, C,     D = C, E = D };    // Compliant by exception
        

        The following examples are non-compliant as enumeration constants have the same implicit values:

        enum E3 { A = 3, B, C, D = 4    };            // 'B' and 'D' have the same value
        enum E4 { A = 3, B, C, D = B, E };            // 'C' and 'E' have the same value
        

        The following example is non-compliant as the use of B + 1 means the exception does not apply.

        enum E5 { A = 3, B, C, D = B + 1 };           // 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