30-03-2017, 09:48 AM
dg1980 has correctly pointed out that there are various ways to satisfy this rule. In MISRA-C:2012 this rule has become a directive (4.11), which highlights that the MISRA-C team is not mandating exactly what a tool should be checking for. Therefore tools will vary in how they perform this check.
In this particular case it CAN BE statically demonstrated that there are no issues of undefined behaviour since the input parameters are valid.
In this particular case it CAN BE statically demonstrated that there are no issues of undefined behaviour since the input parameters are valid.
Posted by and on behalf of the MISRA C Working Group