MISRA C:2025 Rule 19.2

R2026b

The union keyword should not be used

Since R2026b

expand all in page

Description

The union keyword should not be used 1 .

Rationale

If you write to a union member and read the same union member, the behavior is well-defined. But if you read a different member, the behavior depends on the relative sizes of the members. For instance:

  • If you read a union member with wider memory size, the value you read is unspecified.

  • Otherwise, the value is implementation-dependent.

Troubleshooting

If you expect a rule violation but do not see it, refer to Diagnose Why Coding Standard Violations Do Not Appear as Expected.

Examples

expand all

unsigned int zext(unsigned int s)
{
    union                 /* Non-compliant */
    {
        unsigned int ul;
        unsigned short us;
    } tmp;

    tmp.us = s;
    return tmp.ul;        /* Unspecified value */
}

In this example, the 16-bit short field tmp.us is written but the wider 32-bit int field tmp.ul is read. Using the union keyword can cause such unspecified behavior. Therefore, the rule forbids using the union keyword.

Check Information

Group: Overlapping Storage
Category: Advisory
AGC Category: Advisory
PQL Name: std.misra_c_2025.R19_2

Version History

Introduced in R2026b

See Also

Topics

1 All MISRA coding rules and directives are © Copyright The MISRA Consortium Limited 2021.

The MISRA coding standards referenced in the Polyspace® Bug Finder™ documentation are from the following MISRA standards:

  • MISRA C:2004

  • MISRA C:2012

  • MISRA C:2023

  • MISRA C:2025

  • MISRA C++:2008

  • MISRA C++:2023

MISRA and MISRA C are registered trademarks of The MISRA Consortium Limited 2021.