Improve Coverity Scan Integration: GSOC project details

[Gedare Bloom]

On Mon, Mar 2, 2020 at 2:55 AM suyash singh <suyashsingh234 at gmail.com> wrote:
>
> Okay so I found this
> https://www.synopsys.com/content/dam/synopsys/sig-assets/datasheets/coverity-misra-standards-ds-ul.pdf
> and
> https://github.com/ARM-software/tf-issues/issues/549
> Which leads me to believe coverity provides a MISRA scanner.
>
> Is it practical to write a program to check some of the MISRA C rules?
>

The approach to take would be to figure out how to write custom
analyzers in an open-source product such as clang-analyzer or
cppcheck. I will address other comments too.

> On Mon, Mar 2, 2020 at 12:19 PM Sebastian Huber <sebastian.huber at embedded-brains.de> wrote:
>>
>> On 02/03/2020 02:31, Joel Sherrill wrote:
>> >     *THIRD POINT-*
>> >     Enabling and testing MISRA rules.
>> >
>> >
>> > Do you know of a free tool that checks Misra C rules? There are closed
>> > source products that do but I don't know of a FLOSS one.
>>
>> cppcheck seems to have some support:
>>
>> http://cppcheck.sourceforge.net/misra.php
>>
>> My approach to MISRA rules would be to first assess which rules we want
>> for the RTEMS Project. To discuss the rules, you need the MISRA C
>> standard. It is not expensive, but it is also not free. Discussing MISRA
>> rules an a public mailing list is also somewhat peculiar due to
>> copyright issues. The relevant rules should be documented in the RTEMS
>> Software Engineering manual (e.g. a nice list of numbers meaningless to
>> anyone without access to the MISRA C standard). For each rule there
>> should be some guideline how it can be enforced.
>>
>> --
>> Sebastian Huber, embedded brains GmbH
>>
>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>> Phone   : +49 89 189 47 41-16
>> Fax     : +49 89 189 47 41-09
>> E-Mail  : sebastian.huber at embedded-brains.de
>> PGP     : Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel