Re: [PATCH v2] docs/misra: new rules addition

On 12/06/23 11:50, Jan Beulich wrote: On 12.06.2023 11:34, Roberto Bagnara wrote: On 12/06/23 09:33, Jan Beulich wrote: On 09.06.2023 19:45, Stefano Stabellini wrote: @@ -143,6 +163,12 @@ existing codebase are work-in-progress. - Octal constants shall not be used - + * -

Re: [PATCH v2] docs/misra: new rules addition

On 12.06.2023 11:34, Roberto Bagnara wrote: > On 12/06/23 09:33, Jan Beulich wrote: >> On 09.06.2023 19:45, Stefano Stabellini wrote: >>> @@ -143,6 +163,12 @@ existing codebase are work-in-progress. >>>- Octal constants shall not be used >>>- >>> >>> + * - `Rule 7.2 >>>

Re: [PATCH v2] docs/misra: new rules addition

On 12/06/23 09:33, Jan Beulich wrote: On 09.06.2023 19:45, Stefano Stabellini wrote: @@ -133,6 +146,13 @@ existing codebase are work-in-progress. headers (xen/include/public/) are allowed to retain longer identifiers for backward compatibility. + * - `Rule 6.1

Re: [PATCH v2] docs/misra: new rules addition

On 09.06.2023 19:45, Stefano Stabellini wrote: > @@ -133,6 +146,13 @@ existing codebase are work-in-progress. > headers (xen/include/public/) are allowed to retain longer > identifiers for backward compatibility. > > + * - `Rule 6.1 >

[PATCH v2] docs/misra: new rules addition

From: Stefano Stabellini For Dir 1.1, a document describing all implementation-defined behaviour (i.e. gcc-specific behavior) will be added to docs/misra, also including implementation-specific (gcc-specific) appropriate types for bit-field relevant to Rule 6.1. Rule 21.21 is lacking an example