The following rules are removed from the original MISRA rules:
|1.3||Multiple compilers and/or languages shall only be used if there is a common defined interface standard for object code to|
which the language/compilers/assemblers conform.
1.3 is not applicable. We do not use multiple languages but just C.
|1.5||Floating-point implementations should comply with a defined floating-point standard.|
|10.2||The value of an expression of floating type shall not be implicitly converted to a different underlying type if:|
a. it is not a conversion to a wider floating type, or
b. the expression is complex, or
c. the expression is a function argument, or
d. the expression is a return expression.
|10.4||The value of a complex expression of floating type shall only be cast to a floating type which is narrower or of the same size.|
|12.12||The underlying bit representations of floating-point values shall not be used.|
|13.3||Floating-point expressions shall not be tested for equality or inequality.|
|13.4||The controlling expression of a for statement shall not contain any objects of floating type.|
1.5, 10.2, 10.4, 12.12, 13.3, 13.4 are not applicable – we do not use floating point arithmetic (C29).
|3.5||If it is being relied upon, the implementation-defined behavior and packing of bit fields shall be documented.|
|6.4||Bit fields shall only be defined to be of type unsigned int or signed int.|
|6.5||Bit fields of signed type shall be at least two bits long.|
HCC rule C10 and C37 give a more disciplined way of using the bit fields.