MISRA C:2025 Rule 15.1

R2026b

The goto statement should not be used

Since R2026b

expand all in page

Description

The goto statement should not be used 1 .

Rationale

Unrestricted use of goto statements makes the program unstructured and difficult to understand.

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

void foo(void) {
    int i = 0, result = 0;

label1:
    for ( i; i < 5; i++ ) {
        if (i > 2) goto label2;     /* Non-compliant */
    }

label2: {
        result++;
        goto label1;                /* Non-compliant */
    }
}

In this example, the rule is violated when goto statements are used.

Check Information

Group: Control Flow
Category: Advisory
AGC Category: Advisory
PQL Name: std.misra_c_2025.R15_1

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.