public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
	Baraa Jarkas <baraajarkas@live.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: MISRA C
Date: Fri, 15 Oct 2021 17:50:09 +0200	[thread overview]
Message-ID: <fbe663be-fabd-7a3f-5bc6-829dbca3a7cd@hesbynett.no> (raw)
In-Reply-To: <CAH6eHdSQ8sRQZWbULRpe6djAkQ7onx8-bfUwxePomDcE7cT6CA@mail.gmail.com>

On 13/10/2021 21:35, Jonathan Wakely via Gcc-help wrote:
> On Wed, 13 Oct 2021 at 14:11, Baraa Jarkas via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
>>
>> Hi,
>>
>> I would like to know which Misra C Rules are supported by GCC compiler and if there is any document contains these informations.
> 
> What do you mean by "supported"?
> 
> Valid C code that follows MISRA rules can be compiled by GCC, but I
> doubt that's what you mean.
> 
> If you want something to check that the rules are followed, that's not
> what GCC is for. GCC is a compiler. There are static analysis tools
> that can check for conformance to guidelines like MISRA.
> 


I find gcc very useful for static analysis too - much better than many
commercial compilers that support MISRA rule checking.

But many of the MISRA rules would be more suitable in a plugin, perhaps
using David Malcolm's static analyser framework or his Python plugin.

There's also the issue that MISRA is not free (it's cheap - £10, as far
as I remember - but very far from "GPL free").  I don't know the
licensing or copyright complications that might be involved in making a
plugin that referenced rules in MISRA's guidelines.

      reply	other threads:[~2021-10-15 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 13:10 Baraa Jarkas
2021-10-13 19:35 ` Jonathan Wakely
2021-10-15 15:50   ` David Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fbe663be-fabd-7a3f-5bc6-829dbca3a7cd@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=baraajarkas@live.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).