From: Roberto Bagnara <roberto.bagnara@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: roger.pau@citrix.com, bertrand.marquis@arm.com,
michal.orzel@amd.com, xenia.ragiadakou@amd.com,
ayan.kumar.halder@amd.com, consulting@bugseng.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH v2] docs/misra: document the C dialect and translation toolchain assumptions.
Date: Wed, 21 Jun 2023 15:21:30 +0200 [thread overview]
Message-ID: <cbf75735-4baf-bbb8-cae9-9529c277294a@bugseng.com> (raw)
In-Reply-To: <0ba16220-64a6-63bf-a1b8-77dcc847d2ed@suse.com>
On 21/06/23 12:27, Jan Beulich wrote:
> On 20.06.2023 14:10, Roberto Bagnara wrote:
>> + * - static function is used in an inline function with external linkage
>> + - ARM64, X86_64
>> + - Non-documented GCC extension. An inline function with external linkage
>> + can be inlined everywhere. If that calls a static functions, which is
>> + not available everywhere, it is a constraint violation according to
>> + C99 6.7.4p3: "An inline definition of a function with external linkage
>> + shall not contain a definition of a modifiable object with static
>> + storage duration, and shall not contain a reference to an identifier
>> + with internal linkage." A standard-compliant C compiler ought
>> + to diagnose all constraint violations: when it does not, as is the
>> + case for GCC, the behavior is implicitly undefined.
>
> With _spin_lock_cb() taken care of, do we have any left? Or else can this
> be dropped?
Dropped both from the document and the tool configuration.
Roberto
prev parent reply other threads:[~2023-06-21 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 12:10 [XEN PATCH v2] docs/misra: document the C dialect and translation toolchain assumptions Roberto Bagnara
2023-06-20 14:52 ` Jan Beulich
2023-06-20 20:32 ` Stefano Stabellini
2023-06-21 13:11 ` Roberto Bagnara
2023-06-20 14:56 ` Jan Beulich
2023-06-21 13:18 ` Roberto Bagnara
2023-06-20 15:05 ` Jan Beulich
2023-06-21 14:58 ` Roberto Bagnara
2023-06-20 20:31 ` Stefano Stabellini
2023-06-21 10:27 ` Jan Beulich
2023-06-21 13:21 ` Roberto Bagnara [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=cbf75735-4baf-bbb8-cae9-9529c277294a@bugseng.com \
--to=roberto.bagnara@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.com \
/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.