Re: deviations tagging

[Jan Beulich <jbeulich@xxxxxxxx>]

On 15.06.2022 00:47, Stefano Stabellini wrote:
> Roberto was suggesting to use the following different categories for
> tagging deviations. We could pick any "TAG" we like for the in-code
> comments (or other tagging systems).
> 
> I am also CCing the MISRA C team to give them early visibility on this.
> Feel free to provide early feedback if you have any. The plan is to
> discuss it further during the next fusa-sig call and come up with a more
> detailed proposal (including the actual tags, how to use them and more)
> for xen-devel next.

And as early feedback: They all look like they're meant to be used
together with some rule reference (or else there's insufficient context
to know what is being talked about). Yet iirc we said we'd want tool-
agnostic tags, such that the same kind of comments can also be used to
mark e.g. things Coverity has found and we have decided to leave alone.

Jan

> adopted
> 
>    The report should be considered originated by adopted code without any
>    contribution of native code to the report.
> 
> safe
> 
>    The report is correct but the specific behavior is safe under every
>    aspect assumed to be covered by the guideline.
> 
> relied
> 
>    The report is correct but the rule concerns exclusively "developer
>    confusion" or readability matters that are not relevant for adopted code,
>    which is assumed to work as is and it is not meant to be read, reviewed
>    or modified by human programmers.  To be used for adopted code only.
> 
> false-positive
> 
>    In the opinion of the developer the violation report is not correct
>    and the problem has been notified to the tool provider.
>    To be used only for violation reports.
> 
> compliant
> 
>    The developer can prove that the possible non-compliance shown by
>    caution report cannot happen in any situation and can motivate such
>    claim.  To be used only for caution reports.
> 
> false-negative
> 
>    The developer has found a non-compliance not shown by the tool and the
>    problem has been notified to the tool provider.
>