TASKING VX-toolset for ARM User Guide

MISRA-C Rules106.(R)Automatic address may not be assigned to a longer lived object.107.(R)The null pointer shall not be de-referenced.A violation is reported for every pointer dereference that is not guarded by a NULLpointer test.108.(R)All struct/union members shall be fully specified.109.(R)Overlapping variable storage shall not be used.A violation is reported for every union declaration.110.(R)Unions shall not be used to access the sub-parts of larger types.A violation is reported for a union containing a struct member.111.(R)Bit-fields shall have type unsigned int or signed int.112.(R)Bit-fields of type signed int shall be at least 2 bits long.113.(R)All struct/union members shall be named.114.(R)Reserved and standard library names shall not be redefined.115.(R)Standard library function names shall not be reused.x116.(R)Production libraries shall comply with the MISRA C restrictions.x117.(R)The validity of library function parameters shall be checked.118.(R)Dynamic heap memory allocation shall not be used.119.(R)The error indicator errno shall not be used.120.(R)The macro offsetof shall not be used.121.(R) and the setlocale function shall not be used.122.(R)The setjmp and longjmp functions shall not be used.123.(R)The signal handling facilities of shall not be used.124.(R)The library shall not be used in production code.125.(R)The functions atof/atoi/atol shall not be used.126.(R)The functions abort/exit/getenv/system shall not be used.127.(R)The time handling functions of library shall not be used.20.2. MISRA-C:2004This section lists all supported and unsupported MISRA-C:2004 rules.See also Section 4.7.2, C Code Checking: MISRA-C.A number of MISRA-C rules leave room for interpretation. Other rules can only be checked in a limitedway. In such cases the implementation decisions and possible restrictions for these rules are listed.x means that the rule is not supported by the TASKING C compiler. (R) is a required rule, (A) is an advisoryrule.867