MISRA Discussion Forums - 8.17 Functions

Rule 17.3 when function has definition

Thu, 15 Jun 2023 14:32:32 +0000

I wonder if the code below violates rule 17.3:

void dostuff(int x) {
// do some stuff..
}

void func(void) {
dostuff(12);   // <- is 17.3 violated here?
}

Please note that the functions dostuff and func violates rule 8.4 and don't have prototypes.

Question: is 17.3 violated when calling a function that violates rule 8.4?

The rationale for 17.3 also does not apply to my example code as far as I understand:

    If a function is declared implicitly, a C90 compiler will assume
    that the function has a return type of int. Since an implicit
    function declaration does not provide a prototype, a compiler will
    have no information about the number of function parameters and
    their types.

Rule 17.4 and main

Fri, 01 Oct 2021 09:59:21 +0000

Hello,
we are facing a conflict between armclang compiler warning and mandatory MISRA Rule.
The armclang compiler V6.16 seems to require "int main", but if we adhere to Rule 17.4 adding "return 0" at the end of main it is leading to a compiler warning.
(warning: 'return' will never be executed [-Wunreachable-code-return])

Who is having the higher priority here to comply with MISRA?
Is it required to deactivate / ignore the compiler warning at this point?

According to the C Standard, 5.1.2.2.3, paragraph 1 [ISO/IEC 9899:2011], "Reaching the } that terminates the main function returns a value of 0."
Is there another possibility to comply with the MISRA Rule 17.4?

Rule 17.5 and arrays of size 1

Tue, 15 May 2018 22:09:57 +0000

Hello,

Please consider the following case:

Code:
#include 

extern void f(int32_t x[1]);

int32_t glob;

extern void test(void);

void test(void)

{

    f(&glob); /* Allowed under MISRA C 2012 R17.5? */

}

Could you confirm if the intent that this should be a violation of the rule since we are passing a non-array as an argument where an array is expected? I ask only because there is related wording in the C90/99 standard under additive operators that states:

Quote:For the purposes of these operators, a pointer to a nonarray object behaves the same as a
pointer to the first element of an array of length one with the type of the object as its element
type.

Thank you for your help.

Best Regards,

-Greg