Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated reference from C11->C23.

...

  • No linkage: If an identifier has no linkage, then any further declaration using the identifier declares something new, such as a new variable or a new type.

According to the to the C Standard, 6.2.2 paragraph 3 [ISO/IEC 9899:20112024], linkage is determined as follows:

If the declaration of a file scope identifier for:
    - an object contains any of the storage-class specifiers static
 or contexpr;

    - or, a function contains the storage-class specifier static,

 then the identifier has internal linkage.

For an identifier declared with the storage-class specifier extern in a scope in which a prior declaration of that identifier is visible, if the prior declaration specifies internal or external linkage, the linkage of the identifier at the later declaration is the same as the linkage specified at the prior declaration. If no prior declaration is visible, or if the prior declaration specifies no linkage, then the identifier has external linkage.

If the declaration of an identifier for a function has no storage-class specifier, its linkage is determined exactly as if it were declared with the storage-class specifier extern. If the declaration of an identifier for an object has file scope and no does not contain the storage-class specifier static or contexpr, its its linkage is external.

The following identifiers have no linkage: an identifier declared to be anything other than an object or a function; an identifier declared to be a function parameter; a block scope identifier for an object declared without the storage-class specifier extern.


Use of an identifier (within one translation unit) classified as both internally and externally linked is undefined behavior. (see See also undefined behavior 8.) . A translation unit includes the source file together with its headers and all source files included via the preprocessing directive #include.

...

Microsoft Visual Studio 2013 issues no warnings about this code, even at the highest diagnostic levels.

The GCC compiler generates a fatal diagnostic GCC and Clang 14 both generate fatal diagnostics for the conflicting definitions of i2 and i5.

...

Use of an identifier classified as both internally and externally linked is undefined behavior.

Rule

Severity

Likelihood

Remediation Cost

Priority

Level

DCL36-C

Medium

Probable

Medium

P8

L2

Automated Detection

Tool

Version

Checker

Description

Astrée
Include Page
Astrée_V
Astrée_V

static-function-declaration

static-object-declaration

Partially checked
Axivion Bauhaus Suite

Include Page
Axivion Bauhaus Suite_V
Axivion Bauhaus Suite_V

CertC-DCL36Fully implemented
CodeSonar
Include Page
CodeSonar_V
CodeSonar_V

LANG.STRUCT.DECL.NOEXT

Missing External Declaration

Coverity
Include Page
Coverity
6.5
_V
Coverity_V
PW.LINKAGE_CONFLICTImplemented
Cppcheck Premium

Include Page
Cppcheck Premium_V
Cppcheck Premium_V

premium-cert-dcl36-cFully implemented

ECLAIR

Include Page
ECLAIR_V
ECLAIR_V

CC2.DCL36

Fully implemented

GCC
Include Page
GCC_V
GCC_V

 

 



Helix QAC

Include Page
Helix QAC_V
Helix QAC_V

C0625Fully implemented
Klocwork
Include Page
Klocwork_V
Klocwork_V

IF_DEF_IN_HEADER_DECL IF_MULTI_DECL

MISRA.FUNC.STATIC.REDECL

Fully implemented

 

LDRA tool suite
Include Page
LDRA_V
LDRA_V

461 S, 575 S, 2 X

Fully implemented

PC-lint Plus

Include Page
PC-lint Plus_V
PC-lint Plus_V

401, 839, 1051

Fully supported

Splint
Include Page
Splint_V
Splint_V

 

 



Parasoft C/C++test
9.5MISRA-024Fully implementedPRQA QA-C Include PagePRQA QA-C_vPRQA QA-C_v0625 (U)
Include Page
Parasoft_V
Parasoft_V
CERT_C-DCL36-a
Identifiers shall not simultaneously have both internal and external linkage in the same translation unit
Polyspace Bug Finder

Include Page
Polyspace Bug Finder_V
Polyspace Bug Finder_V

CERT C: Rule DCL36-C


Checks for inconsistent use of static and extern in object declarations (rule partially covered)

RuleChecker

Include Page
RuleChecker_V
RuleChecker_V

static-function-declaration

static-object-declaration
Partially checked
TrustInSoft Analyzer

Include Page
TrustInSoft Analyzer_V
TrustInSoft Analyzer_V

non-static declaration follows static declaration

Partially verified.

Fully implemented

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Related Guidelines

Key here (explains table format and definitions)

Taxonomy

Taxonomy item

Relationship

MISRA C:2012Rule 8.2 (required)Prior to 2018-01-12: CERT: Unspecified Relationship
MISRA C:2012Rule 8.4 (required)Prior to 2018-01-12: CERT: Unspecified Relationship
MISRA C:2012Rule 8.8 (required)Prior to 2018-01-12: CERT: Unspecified Relationship
MISRA C:2012Rule 17.3 (mandatory)Prior to 2018-01-12: CERT: Unspecified Relationship

Bibliography

...



...

Image Modified Image Modified Image Modified