From: Paolo Bonzini <pbonzini@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>,
"Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH for-8.0 1/3] async: Suppress GCC13 false positive in aio_bh_poll()
Date: Tue, 21 Mar 2023 14:02:35 +0100 [thread overview]
Message-ID: <44a1041b-62b3-f779-7c8a-6a92123c8f1f@redhat.com> (raw)
In-Reply-To: <fabc9edf-697e-41d3-101a-bd7a6ddda84a@redhat.com>
On 3/21/23 13:16, Cédric Le Goater wrote:
>
> + /*
> + * GCC13 [-Werror=dangling-pointer=] complains that the local variable
> + * 'slice' is being stored in the global list 'ctx->bh_slice_list'.
> + */
> +#pragma GCC diagnostic push
> +#pragma GCC diagnostic ignored "-Wdangling-pointer="
> QSIMPLEQ_INSERT_TAIL(&ctx->bh_slice_list, &slice, next);
> +#pragma GCC diagnostic pop
>
> while ((s = QSIMPLEQ_FIRST(&ctx->bh_slice_list))) {
> QEMUBH *bh;
Yeah, that's clearer. Maybe even add "but the list is emptied before
this function returns".
> May be that's more explicit. I wonder if we need to ifdef clang also.
I think clang understand the GCC pragma as well.
Paolo
next prev parent reply other threads:[~2023-03-21 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 8:33 [PATCH for-8.0 0/3] Fixes for GCC13 Cédric Le Goater
2023-03-21 8:33 ` [PATCH for-8.0 1/3] async: Suppress GCC13 false positive in aio_bh_poll() Cédric Le Goater
2023-03-21 10:22 ` Paolo Bonzini
2023-03-21 10:30 ` Daniel P. Berrangé
2023-03-21 10:57 ` Paolo Bonzini
2023-03-21 11:15 ` Stefan Hajnoczi
2023-03-21 11:57 ` Paolo Bonzini
2023-03-21 12:16 ` Cédric Le Goater
2023-03-21 13:02 ` Paolo Bonzini [this message]
2023-03-21 8:33 ` [PATCH for-8.0 2/3] target/s390x: Fix float_comp_to_cc() prototype Cédric Le Goater
2023-03-21 9:37 ` Philippe Mathieu-Daudé
2023-03-22 3:48 ` Richard Henderson
2023-03-22 6:51 ` Thomas Huth
2023-03-21 8:33 ` [PATCH for-8.0 3/3] target/ppc: Fix helper_pminsn() prototype Cédric Le Goater
2023-03-21 11:07 ` Daniel Henrique Barboza
2023-03-22 3:49 ` Richard Henderson
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=44a1041b-62b3-f779-7c8a-6a92123c8f1f@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@kaod.org \
--cc=clg@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).