Welcome to the MISRA discussion forum

Hi,

Of the 191 undefined behaviours listed in C99, there are 61 that have no associated MISRA guideline. Checking all of these is particularly labourious, especially as the list in Annex J is not numbered.

How do people go about checking conformity with this catch-all rule?

Does anyone globally deviate from this rule, since the most important and most likely behaviours are addressed by other guidelines and checking the others is not practical?

Thanks.

Does the following code example violate Rule 2.2, due to the left shift?

[code]#define BITSET(reg, bit) ((reg) |= (uint8_t)(1u

Hello all,

We use MISRA-2004. Do you need to migrate to MISRA-2012? Is MISRA-2012 state of the art?

Any recommendations? Official statements? Decision matrix?

Greetings
Adam

Does 11.0.1 "Member data in non-POD class types shall be private." apply to all data members, or only non-static data members?

In particular, I'm interested whether the constant in this code violates 11.0.1:

Is it just me or is anybody else having trouble too (tested with IE 11 and Firefox 47)?

Rule 2.3 mentions "type declaration".
Rule 2.5 mentions "macro declaration".

But I think the type should not be declared but defined by "typedef".
I also think the macro should not be decalred but defined by "#define".

MISRA Study Group in Japan is confused when translating the guidelines.

Thank you

The following question has been submitted to the working group.

Please can you explain which of the following are non-compliant with rule 10.3.

Quote:a non-negative integer constant expression of essentially signed type may be assigned to an object of essentially unsigned type if its value can be represented in that type

According to Rule 4-5-1 sizeof(bool_type_variable) is not allowed, although it is very meaningful in serialization.
Is this intentional?
If so then why?

Does Rule 12.5 from AMD-1 apply to unsized array parameters (those without a size between the brackets)? E.g.:

MISRA has published a mapping of MISRA C coverage of the "C Secure" requirements found in ISO/IEC TS 17961:2013. This mapping shows that for freestanding applications, MISRA C already has excellent coverage of the "C Secure" requirements. Additional guidelines are provided in MISRA C:2012 Amendment 1 to improve the coverage of the security concerns highlighted by the "C Secure" guidelines.

Both documents are available as free downloads from the "Resources" section of this Bulletin Board.

If you have questions on the new Guidelines then they can be asked under the relevant forum topic (e.g. a question about Rule 12.5 should be added under "MISRA C > MISRA C:2012 guidelines > 8.12 Expressions").