Page History

Linkage can make an identifier declared in different scopes or declared multiple times within the same scope refer to the same object or function. Identifiers are classified as externally linked, internally linked, or not linked. These three kinds of linkage have the following characteristics [Kirch-Prinz 2002]:

• External linkage:

An identifier declared in different scopes or multiple times within the same scope can be made to refer to the same object or function by _linkage_.  An identifier can be classified as _externally linked_, _internally linked_, or _not-linked_.  These three kinds of linkage have the following characteristics \[[Kirch-Prinz 02]\]:

• External linkage. An identifier with external linkage represents the same object or function throughout the entire program, that is, in all compilation units and libraries belonging to the program. The identifier is available to the linker. When a second declaration of the same identifier with external linkage occurs, the linker associates the identifier with the same object or function.

• Internal linkage.: An identifier with internal linkage represents the same object or function within a given translation unit. The linker has no information about identifiers with internal linkage. Consequently, these identifiers are internal to the translation unit.

• 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.

Wiki MarkupAccording to C99 \[to the C Standard, 6.2.2 paragraph 3 [ISO/IEC 9899:1999|AA. C References#ISO/IEC 9899-1999]\2024], 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 causes is undefined behavior. (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.

...

The following table identifies the linkage assigned to an object that is declared twice in a single translation unit. The column designates the first declaration, and the row designates the redeclaration.

Image Added

Noncompliant Code Example

In this non-compliant noncompliant code example, i2 and i5 are defined as having both internal and external linkage. Future use of either identifier results in undefined behavior.

int i1 = 10;         /* definitionDefinition, external linkage */
static int i2 = 20;  /* definitionDefinition, internal linkage */
extern int i3 = 30;  /* definitionDefinition, external linkage */
int i4;              /* tentativeTentative definition, external linkage */
static int i5;       /* tentativeTentative definition, internal linkage */

int i1;  /* validValid tentative definition */
int i2;  /* not validUndefined, linkage disagreement with previous */
int i3;  /* validValid tentative definition */
int i4;  /* validValid tentative definition */
int i5;  /* not validUndefined, linkage disagreement with previous */

int main(void) {
  /* ... */
  return 0;
}

Implementation Details

Both Microsoft Visual Studio 2003 and Microsoft Visual Studio 2005 compile this non-compliant code example without warning 2013 issues no warnings about this code, even at the highest diagnostic levels. Microsoft Visual Studio 2008 does provide warnings at the default warning level. The GCC compiler generates a fatal diagnostic

GCC and Clang 14 both generate fatal diagnostics for the conflicting definitions of i2 and i5.

...

This compliant solution does not include conflicting definitions.:

int i1 = 10;         /* definitionDefinition, external linkage */
static int i2 = 20;  /* definitionDefinition, internal linkage */
extern int i3 = 30;  /* definitionDefinition, external linkage */
int i4;              /* tentativeTentative definition, external linkage */
static int i5;       /* tentativeTentative definition, internal linkage */

int main(void) {
  /* ... */
  return 0;
}

Risk Assessment

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

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-DCL36	Fully implemented
CodeSonar	Include Page CodeSonar_V CodeSonar_V	LANG.STRUCT.DECL.NOEXT	Missing External Declaration
Coverity	Include Page Coverity_V Coverity_V	PW.LINKAGE_CONFLICT	Implemented
Cppcheck Premium	Include Page Cppcheck Premium_V Cppcheck Premium_V	premium-cert-dcl36-c	Fully 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	C0625	Fully implemented
Klocwork	Include Page Klocwork_V Klocwork_V	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	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.

Related Vulnerabilities

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

References

...

Related Guidelines

Key here (explains table format and definitions)

Bibliography

...

...

...

...

...

...

...

Image Added Image Added Image Added 02|AA. C References#Kirch-Prinz 02]\] \[[MISRA 04|AA. C References#MISRA 04]\] Rule 8.1DCL35-C. Do not convert a function pointer to an incompatible type      02. Declarations and Initialization (DCL)       03. Expressions (EXP)