All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, consulting@bugseng.com,
	Simone Ballarin <simone.ballarin@bugseng.com>,
	Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [XEN PATCH v2 7/7] automation/eclair_analysis: avoid violation of MISRA Rule 2.1
Date: Tue, 19 Dec 2023 09:00:27 +0100	[thread overview]
Message-ID: <8707dd8023b0e05efaf46e7afb3b85cb@bugseng.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2312181743250.3175268@ubuntu-linux-20-04-desktop>

On 2023-12-19 02:43, Stefano Stabellini wrote:
> On Mon, 18 Dec 2023, Stefano Stabellini wrote:
>> On Mon, 18 Dec 2023, Nicola Vetrini wrote:
>> > The presence of an unlinked object file triggers a violation
>> > of MISRA C Rule 2.1, which is deviated, as it's not part of
>> > the final Xen binary.
>> >
>> > No functional change.
>> >
>> > Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
>> 
>> Acked-by: Stefano Stabellini <sstabellini@kernel.org>
>> 
>> 
>> > ---
>> >  automation/eclair_analysis/ECLAIR/deviations.ecl | 5 +++++
>> >  1 file changed, 5 insertions(+)
>> >
>> > diff --git a/automation/eclair_analysis/ECLAIR/deviations.ecl b/automation/eclair_analysis/ECLAIR/deviations.ecl
>> > index 85741a2c01a9..e3de0fb2adf8 100644
>> > --- a/automation/eclair_analysis/ECLAIR/deviations.ecl
>> > +++ b/automation/eclair_analysis/ECLAIR/deviations.ecl
>> > @@ -28,6 +28,11 @@ not executable, and therefore it is safe for them to be unreachable."
>> >  -config=MC3R1.R2.1,ignored_stmts+={"any()", "pure_decl()"}
>> >  -doc_end
>> >
>> > ++-doc_begin="The following autogenerated file is not linked deliberately."
>> > ++-file_tag+={C_runtime_failures,"^automation/eclair_analysis/C-runtime-failures\\.rst\\.c$"}
>> > ++-config=MC3R1.R2.1,reports+={deliberate, "any_area(any_loc(file(C_runtime_failures)))"}
>> > ++-doc_end
> 
> Would it make sense to add it to exclude-list instead?

I don't think so, because if some documentation about runtime error that 
is supposed to be here is missing it won't be obvious that the file that 
needs to be fixed is this. Moreover, you'd need to put the path of the 
generated .c file there, which I'm not sure how well it would behave 
w.r.t. other tooling.

-- 
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)


      reply	other threads:[~2023-12-19  8:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 10:17 [XEN PATCH v2 0/7] address violations of MISRA C:2012 Rule 2.1 Nicola Vetrini
2023-12-18 10:17 ` [XEN PATCH v2 1/7] xen/shutdown: address " Nicola Vetrini
2023-12-19  1:31   ` Stefano Stabellini
2023-12-18 10:17 ` [XEN PATCH v2 2/7] x86/mm: " Nicola Vetrini
2023-12-19  1:33   ` Stefano Stabellini
2023-12-19 10:56   ` Jan Beulich
2023-12-18 10:17 ` [XEN PATCH v2 3/7] xen/arm: " Nicola Vetrini
2023-12-19  1:35   ` Stefano Stabellini
2023-12-18 10:17 ` [XEN PATCH v2 4/7] xen/arm: traps: add ASSERT_UNREACHABLE() where needed Nicola Vetrini
2023-12-19  1:36   ` Stefano Stabellini
2023-12-18 10:17 ` [XEN PATCH v2 5/7] x86/platform: removed break to address MISRA C:2012 Rule 2.1 Nicola Vetrini
2023-12-19  1:37   ` Stefano Stabellini
2023-12-18 10:17 ` [XEN PATCH v2 6/7] xen/arm: vcpreg: address violation of MISRA C " Nicola Vetrini
2023-12-19  1:39   ` Stefano Stabellini
2023-12-18 10:17 ` [XEN PATCH v2 7/7] automation/eclair_analysis: avoid violation of MISRA " Nicola Vetrini
2023-12-19  1:40   ` Stefano Stabellini
2023-12-19  1:43     ` Stefano Stabellini
2023-12-19  8:00       ` Nicola Vetrini [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=8707dd8023b0e05efaf46e7afb3b85cb@bugseng.com \
    --to=nicola.vetrini@bugseng.com \
    --cc=cardoe@cardoe.com \
    --cc=consulting@bugseng.com \
    --cc=simone.ballarin@bugseng.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.