From: Cornelia Huck <cohuck@redhat.com>
To: "Chenyi Qiang" <chenyi.qiang@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>
Cc: Chenyi Qiang <chenyi.qiang@intel.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/2] configure: Add -Wno-gnu-variable-sized-type-not-at-end
Date: Fri, 09 Sep 2022 12:52:57 +0200 [thread overview]
Message-ID: <878rmsom46.fsf@redhat.com> (raw)
In-Reply-To: <20220909035758.17434-2-chenyi.qiang@intel.com>
On Fri, Sep 09 2022, Chenyi Qiang <chenyi.qiang@intel.com> wrote:
> In recent linux headers update to v6.0-rc, it switched GNU
Maybe
"A Linux headers update to v6.0-rc switches some definitions from the
GNU..."
?
> 'zero-length-array' extension to the C-standard-defined flexible array
> member. e.g.
>
> struct kvm_msrs {
> __u32 nmsrs; /* number of msrs in entries */
> __u32 pad;
>
> - struct kvm_msr_entry entries[0];
> + struct kvm_msr_entry entries[];
> };
>
> Those (unlike the GNU zero-length-array) have some extra restrictions like
> 'this must be put at the end of a struct', which clang build would complain
> about. e.g. the current code
>
> struct {
> struct kvm_msrs info;
> struct kvm_msr_entry entries[1];
> } msr_data = { }
>
> generates the warning like:
>
> target/i386/kvm/kvm.c:2868:25: error: field 'info' with variable sized
> type 'struct kvm_msrs' not at the end of a struct or class is a GNU
> extension [-Werror,-Wgnu-variable-sized-type-not-at-end]
> struct kvm_msrs info;
> ^
> In fact, the variable length 'entries[]' field in 'info' is zero-sized in
> GNU defined semantics, which can give predictable offset for 'entries[1]'
> in local msr_data. The local defined struct is just there to force a stack
> allocation large enough for 1 kvm_msr_entry, a clever trick but requires to
> turn off this clang warning.
>
> Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Signed-off-by: Chenyi Qiang <chenyi.qiang@intel.com>
> ---
> configure | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2022-09-09 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 3:57 [PATCH v2 0/2] Update linux headers to v6.0-rc4 and fix the clang build error Chenyi Qiang
2022-09-09 3:57 ` [PATCH v2 1/2] configure: Add -Wno-gnu-variable-sized-type-not-at-end Chenyi Qiang
2022-09-09 10:52 ` Cornelia Huck [this message]
2022-09-09 3:57 ` [PATCH v2 2/2] Update linux headers to v6.0-rc4 Chenyi Qiang
2022-09-09 10:55 ` Cornelia Huck
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=878rmsom46.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@redhat.com \
--cc=chenyi.qiang@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.