Workshop #5 Proposal - Preliminary analysis of a Linux configuration wrt some MISRA C:2012 mandatory guidelines
Preliminary analysis of a Linux configuration wrt some MISRA C:2012 mandatory guidelines
*_What you hope to accomplish in the session_*:
I would like to share the results of this preliminary analysis
in order to come to some understanding whether MISRA C:2012
compliance for Linux is conceivable or not.
*_Any critical participants needed for the discussion_*:
*_Estimated time needed the session_*:
Please note: I am only available on September 30th.
Roberto Bagnara, Ph.D.
CEO/CTO, BUGSENG (http://bugseng.com)
Member, ISO/IEC JTC1/SC22/WG14 - C Standardization Working Group
Member, MISRA C Working Group
Mobile: +39 339 8593517
On Wed, Sep 9, 2020 at 3:49 PM Roberto Bagnara
I like this proposal and I think it is a great opportunity for the
MISRA C Working Group to learn from the best practices of one of the
largest code repositories with code written in C (maybe even the
largest?) and one of the largest public available records (maybe even
the largest?) of many years of code review on C source code.
Some things to note:
1. Of course, the kernel is not really written in C; it is a C syntax,
but the semantics of the kernel code follows a different semantics
than the C programming language.
2. The relevant rules for code reviews have evolved from a practical
need to do code review at large scale effectively and efficiently. So,
it is much more grounded around practical aspects of code review than
anything else, e.g., purely academic considerations.
What is the emprical basis that MISRA C:2012 is grounded on?
And what is the track record of competence of the authors that
developed the MISRA coding guidelines?
E.g., how many hours of code review of C code have the MISRA authors
been doing in their history? Do we have public evidence of that?