Static Code Analysis. Compliance with MISRA-C 2004.
in [DSP]
|
Prev: NEED HELP - MUSICAL INSTRUMENT INVENTOR NEEDS A BRILLIANT DSP DESIGNER ASAP!
Next: Simple hack to get $500 to your home
From: Rich Webb on 9 Jun 2010 19:57 On Thu, 10 Jun 2010 00:07:46 +0200, "Frank" <Frank(a)invalidmail.com> wrote: >Hello, > >Any recommendations on some static code analysis tools which checks for >compliance with MISRA-C 2004 ? There's PC-Lint http://www.gimpel.com/html/misra.htm From the user manual: "The Motor Industry Reliability Association (MIRA) released a programming guideline for C in 1998 (sometimes referred to as MISRA C1), and a revised version was released in 2004 (MISRA C2). In 2008, MIRA released guidelines for C++ (MISRA C++). PC-Lint/FlexeLint have supported checks for the available MISRA guidelines since early 2001, and we intend for Lint to provide ongoing and increasing support for these guidelines." I use it for general static checking, not MISRA in particular, and have no specific knowledge as to how well or completely it addresses the MISRA requirements. -- Rich Webb Norfolk, VA
From: steveu on 9 Jun 2010 23:14 >On 06/09/2010 03:07 PM, Frank wrote: >> Hello, >> >> Any recommendations on some static code analysis tools which checks for >> compliance with MISRA-C 2004 ? > >I wonder if the Toyota engine control system code is compliant -- I'll >bet it is. I expect it is MISRA compliant, and I expect being MISRA compliant helped their quality. However, if they had the code developed in an SEI CMM level 5 certified shop, that would explain everything. :-) Steve
From: Andreas Huennebeck on 14 Jun 2010 03:45
Frank wrote: > Any recommendations on some static code analysis tools which checks for > compliance with MISRA-C 2004 ? We use Parasofts C++Test. It contains three sets of rules for MISRA: - MISRA C (57 rules) - MISRA C 2004 (193 rules) - MISRA C++ 2008 (263 rules) C++Test is mainly designed for personal use on a workstation (with team support) but we don't use it that way - we use the server version which runs once per week through all source code and mails any warnings to the programmer who owns the corresponding piece of code. We started with version 6.9.x and now with version 7.3 most problems with the tool have been fixed by Parasoft. bye Andreas -- Andreas H�nnebeck | email: acmh(a)gmx.de ----- privat ---- | www : http://www.huennebeck-online.de Fax/Anrufbeantworter: 0721/151-284301 GPG-Key: http://www.huennebeck-online.de/public_keys/andreas.asc PGP-Key: http://www.huennebeck-online.de/public_keys/pgp_andreas.asc |