Welcome to the MISRA discussion forum

Hi All,

Would you please advise me if a macro containing both assembly and C code
is a violation of Dir 4.3?

Example:
#define M_def do { asm( "mv r0,r1" ); use_uint32( 0 ); } while( 0 )

Please note that 'use_uint32( 0 );' is a function call.

Regards,
Tad

Where can I find a document that describes the mapping between MISRA rules and ISO26262 and IEC61508? Thank you.

In the following code I would like to know which of the casts are compliant for rule 11.8?

[code]
const int a[10];
int *pi;
int **ppi;
const int **cppi;
const float **cppf;

void f() {
pi = (int*) &a; /* int *

Hi all,
sorry for the late notice on this I failed to get logged in here until now.

There has been some discussion between members of MISRA members and contributors to the CERT standard for secure c, leading to the creation of a new study group as outlined in the email at
https://lists.trustable.io/pipermail/tru...00181.html

I wonder if other MISRA folks might be interested to get involved?

br
Paul

Hello,

The rule's title includes "types", but the body of the rule does not specify further whether this is meant for typedefs only, or for complex classes as well.
For example, a class only used in a single function: should it be moved into the function? That would work against the typical ideas of short functions and separation of responsibilities. Could you please clarify MISRA's intention here?

MISRA C: 2004 has Rule 13.3 (required): Floating-point expressions shall not be tested for equality or inequality.

This rule is very useful. We use Mathworks/Polyspace for static analysis. We can find issues of (floating variable == or != 0.0) by turning on MISRA C: 2004, but we miss this check by using MISRA C:2012.

We want to always apply the latest MISRA C standard, but not sure which rule in MISRA C: 2012 matches rule 13.3 of MISRA C: 2004?

This suite of files is intended to illustrate issues addressed by the MISRA C rules as expressed in:

• MISRA C:2012 Guidelines for the use of the C language in critical systems, ISBN 978-1-906400-10-1 paperback and ISBN 978-1-906400-11-8 PDF.
  
• MISRA C:2012 Amendment 1Additional security guidelines for MISRA C:2012, ISBN 978-1-906400-16-3 PDF.
  

Attached Files

  Example_Suite_2016_11_01.zip (Size: 169.83 KB / Downloads: 75)

Hi,

the rule text only mentions classes, not structs.
Now, in C++ struct and class are synonyms, except that by default everything is public in a struct.
So, does this rule implicitly apply to all structs as well?
Thank you.

The following is the example reported for Rule 2.2 (dead code):

Quote:In this example, it is assumed that the object pointed to by p is used in other functions.