From: Jan Beulich <jbeulich@suse.com>
To: Nicola Vetrini <nicola.vetrini@bugseng.com>
Cc: consulting@bugseng.com,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Dmytro Prokopchuk1" <dmytro_prokopchuk1@epam.com>
Subject: Re: [PATCH] misra: deviate explicit cast for Rule 11.1
Date: Tue, 29 Jul 2025 09:26:14 +0200 [thread overview]
Message-ID: <4708ddca-2079-491d-9b1a-031ab66988b1@suse.com> (raw)
In-Reply-To: <aa6c034443b495fdf13eaf88487a94b1@bugseng.com>
On 28.07.2025 21:17, Nicola Vetrini wrote:
> On 2025-07-28 20:58, Dmytro Prokopchuk1 wrote:
>> It works.
>> The violation "non-compliant cast: implicit cast from `void(*)(void*)'
>> to `void(*)(void*)'" is gone.
>>
>
> Great. Now what would be really useful is a way to abstract this more
> nicely (I was able to write this only by looking at the AST). However
> noreturn is probably about the only attribute that has a repercussion on
> the decl and is safe to cast away, unless I'm mistaken.
Not sure what you mean by "repercussion" here, and hence my remark may be
entirely meaningless, but: const and pure are also examples of
attributes which are safe to cast away, aiui. In fact, given the sheer
number of attributes, I would be surprised if there weren't more.
Jan
next prev parent reply other threads:[~2025-07-29 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 20:27 [PATCH] misra: deviate explicit cast for Rule 11.1 Dmytro Prokopchuk1
2025-07-28 9:56 ` Jan Beulich
2025-07-28 10:49 ` Andrew Cooper
2025-07-28 17:43 ` Nicola Vetrini
2025-07-28 18:03 ` Dmytro Prokopchuk1
2025-07-28 18:58 ` Dmytro Prokopchuk1
2025-07-28 19:17 ` Nicola Vetrini
2025-07-29 7:26 ` Jan Beulich [this message]
2025-07-29 11:03 ` Nicola Vetrini
2025-07-28 13:09 ` Dmytro Prokopchuk1
2025-07-28 13:23 ` Jan Beulich
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=4708ddca-2079-491d-9b1a-031ab66988b1@suse.com \
--to=jbeulich@suse.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=dmytro_prokopchuk1@epam.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger.pau@citrix.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.