<![CDATA[MISRA Discussion Forums - 6.3 Documentation]]>

<![CDATA[MISRA Discussion Forums - 6.3 Documentation]]> https://forum.misra.org.uk/ Thu, 05 Nov 2026 15:13:15 +0000 MyBB <![CDATA[Issues covered by rule 3.1]]> https://forum.misra.org.uk/showthread.php?tid=931 Wed, 09 Jan 2013 05:44:02 +0000 mtempest]]> https://forum.misra.org.uk/showthread.php?tid=931
As I understand it, rule 3.1 is a "catch all" rule that addresses all of the implementation-defined behaviour not addressed by the other rules. However, MISRA-C:2004 does not explicitly list all of those issues, so it is not possible to tell at a glance exactly what falls under rule 3.1. This creates some difficulty determining the extent to which our static analysis software enforces the MISRA rules, and therefore also when enforcing the delta with manual review.

I could draw up a list of those issues using MISRA-C:2004 Appendix G as a guide to determining which of the issues in ISO/IEC 9899:1990 Appendix G are addressed by other rules, and seeing what is left. I could do this, but it is not a 5-minute exercise (for me) and I suspect that this work has already been done many times before now.

Has a list like that been published on the web anywhere? I've tried googling for it, but to no avail.

Kind regards
Michael]]>
As I understand it, rule 3.1 is a "catch all" rule that addresses all of the implementation-defined behaviour not addressed by the other rules. However, MISRA-C:2004 does not explicitly list all of those issues, so it is not possible to tell at a glance exactly what falls under rule 3.1. This creates some difficulty determining the extent to which our static analysis software enforces the MISRA rules, and therefore also when enforcing the delta with manual review.

I could draw up a list of those issues using MISRA-C:2004 Appendix G as a guide to determining which of the issues in ISO/IEC 9899:1990 Appendix G are addressed by other rules, and seeing what is left. I could do this, but it is not a 5-minute exercise (for me) and I suspect that this work has already been done many times before now.

Has a list like that been published on the web anywhere? I've tried googling for it, but to no avail.

Kind regards
Michael]]> <![CDATA[Rule 3.4: All uses of the #pragma directive shall be...]]> https://forum.misra.org.uk/showthread.php?tid=711 Tue, 02 Mar 2010 11:32:59 +0000 mshearer123]]> https://forum.misra.org.uk/showthread.php?tid=711 What exactly does this rule mean?
How do i document a #pragma?

thanks,

Matt]]> What exactly does this rule mean?
How do i document a #pragma?

thanks,

Matt]]> <![CDATA[Rule 3.6: Supplied Libraries Compliance Check]]> https://forum.misra.org.uk/showthread.php?tid=688 Mon, 16 Nov 2009 18:21:46 +0000 MichelCampmas]]> https://forum.misra.org.uk/showthread.php?tid=688 However, rule 3.6 requires that all libraries (including the ones provided with the compiler) be "subjected to appropriate validation".
Could you expand on what this means in regards to standard libraries? Do we need to require the vendor to certify he is MISRA compliant? If not possible, does this means we have to write our own version, so that we are sure it is compliant?
Thanks
Michel Campmas
Cypress Semiconductor]]> However, rule 3.6 requires that all libraries (including the ones provided with the compiler) be "subjected to appropriate validation".
Could you expand on what this means in regards to standard libraries? Do we need to require the vendor to certify he is MISRA compliant? If not possible, does this means we have to write our own version, so that we are sure it is compliant?
Thanks
Michel Campmas
Cypress Semiconductor]]> <![CDATA[Rule 3.6: Reserved words and standard library function names]]> https://forum.misra.org.uk/showthread.php?tid=478 Wed, 12 Mar 2008 11:39:10 +0000 tria1312]]> https://forum.misra.org.uk/showthread.php?tid=478
I'm using a tool from the USA called codechk.

When performing check on my code I get this message:

Code:
u16_t f29( void );

Quote:error: (REQUIRED) MISRA rule 116 ( 3.6 ) violated: Reserved words and standard library function names shall not be used { DECL }

But I dont see any reserved words or standard library function names. Can anyone help me out? Do you need some more code or infos?

Bjoern]]>
I'm using a tool from the USA called codechk.

When performing check on my code I get this message:

Code:
u16_t f29( void );

Quote:error: (REQUIRED) MISRA rule 116 ( 3.6 ) violated: Reserved words and standard library function names shall not be used { DECL }

But I dont see any reserved words or standard library function names. Can anyone help me out? Do you need some more code or infos?

Bjoern]]> <![CDATA[Rule 3.5: bitfields and basic types]]> https://forum.misra.org.uk/showthread.php?tid=445 Fri, 25 Jan 2008 10:00:43 +0000 Reggi]]> https://forum.misra.org.uk/showthread.php?tid=445
i have a question about the type in bitfields.

In the example in rule 3.5 there is the note \"Note: use of basic types is required\"

In rule 6.3 it says: \"typedefs are not considered necessary in the specification of bit-field types.\"

So typedefs are not forbidden for bitfields.

I don't anderstand the stÃ¤tement in the example of rule 3.5.

Why are basic types required here?

Do you have an explanation, why i should write

unsigned int x_set:1

and not

uint32_t ? x_set:1?

Thanks,
Regine]]>
i have a question about the type in bitfields.

In the example in rule 3.5 there is the note \"Note: use of basic types is required\"

In rule 6.3 it says: \"typedefs are not considered necessary in the specification of bit-field types.\"

So typedefs are not forbidden for bitfields.

I don't anderstand the stÃ¤tement in the example of rule 3.5.

Why are basic types required here?

Do you have an explanation, why i should write

unsigned int x_set:1

and not

uint32_t ? x_set:1?

Thanks,
Regine]]> <![CDATA[What is the character set referred to in Rule 3.2?]]> https://forum.misra.org.uk/showthread.php?tid=41 Fri, 09 Sep 2005 13:37:09 +0000 Gavin McCall]]> https://forum.misra.org.uk/showthread.php?tid=41
Answer: MISRA C Steering Team

There are two character sets.
The source code is written in one character set.
The program can execute with input/output in a second character set.
These may or may not be the same.
Both the basic source character set and the basic execution character sets shall be documented.
This rule allows free choice of character sets for coding and execution. This use shall be documented.]]>
Answer: MISRA C Steering Team

There are two character sets.
The source code is written in one character set.
The program can execute with input/output in a second character set.
These may or may not be the same.
Both the basic source character set and the basic execution character sets shall be documented.
This rule allows free choice of character sets for coding and execution. This use shall be documented.]]>