[C-safe-secure-studygroup] (no subject)

Robert Seacord rcseacord at gmail.com
Wed Jul 11 19:40:51 BST 2018


I made a couple of changes to the Conformance section based on our call
today.  You can see these here:

https://gitlab.com/trustable/C_Safety_and_Security_Rules_Study_Group/blob/master/TS_17961.md#conformance


I've also pasted the text below. Changed line are highlighted in yellow.

Conformance
In this Technical Specification, “shall” is to be interpreted as a
requirement on an analyzer; conversely, “shall not” is to be interpreted
as a prohibition.
Various types of programs (such as compilers or specialized analyzers)
can be used to check if a program contains any violations of the coding
rules specified in this Technical Specification. In this Technical
Specification, all such checking programs are called analyzers. An
analyzer can claim conformity with this Technical Specification.
Programs that do not yield any diagnostic when analyzed by a conforming
analyzer cannot claim conformity to this Technical Specification.
A conforming analyzer shall produce a diagnostic for each distinct rule
in this Technical Specification upon detecting a violation of that rule,
except in the case that the same program text violates multiple rules
simultaneously, where a conforming analyzer may aggregate diagnostics
but shall produce at least one diagnostic.
NOTE 1 The diagnostic message might be of the form:
Accessing freed memory in function abc, file xyz.c, line nnn.

NOTE 2 This Technical Specification does not require an analyzer to
produce a diagnostic message for any violation of any syntax rule or
constraint specified by the C Standard.
Conformance is defined only with respect to source code that is visible
to the analyzer. Binary-only libraries, and calls to them, are outside
the scope of these rules.
For each decidable rule, the analyzer shall report a diagnostic for all
rule violations.
For each undecidable rule, the analyzer shall report a diagnostic for at
least one
program that contains a violation of that rule.
For each rule, the analyzer shall document whether its analysis is
guaranteed to report all violations of that rule and shall document its
accuracy with respect to avoiding false positives and false negatives.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.trustable.io/pipermail/c-safe-secure-studygroup/attachments/20180711/5e514df9/attachment.html>


More information about the C-safe-secure-studygroup mailing list