JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

CodeSonar® 9.2p0 CONFIDENTIAL CodeSecure Inc
C and C++


LANG.STRUCT.MISRS : Misplaced Return Statement

Summary

A function's return statement is not at the end of the function.

Properties

Class Name Misplaced Return Statement
Significance style
Mnemonic LANG.STRUCT.MISRS
Categories
MisraC2025 MisraC2025:15.5 A function should have a single point of exit at the end
MisraC2023 MisraC2023:15.5 A function should have a single point of exit at the end
Misra2012 Misra2012:15.5 A function should have a single point of exit at the end
Misra2004 Misra2004:14.7 A function shall have a single point of exit at the end of the function
MisraC++2008 MisraC++2008:6-6-5 A function shall have a single point of exit at the end of the function.
Availability Available for C and C++.
Enabling Checks for this warning class are disabled by default, and require the unnormalized C ASTs for the project. To enable them, add the following WARNING_FILTER rule and RETAIN_UNNORMALIZED_C_AST specification to the project configuration file.
RETAIN_UNNORMALIZED_C_AST = Yes
WARNING_FILTER += allow class="Misplaced Return Statement"
Note that retaining the unnormalized ASTs will increase the disk space used to store the project representation, and may make the analysis take longer.

Example

int lang_struct_misrs(int i){ /* 'Misplaced Return Statement' warning issued here. */
    int x=0;
    while (1){
        if (x >= i) return x;
        x++;
    }
}

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.

 

To report problems with this documentation, please visit https://support.codesecure.com/.