From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"patches@linaro.org" <patches@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] atomic.h: Work around gcc spurious "unused value" warning
Date: Thu, 10 May 2018 07:43:32 -0700 [thread overview]
Message-ID: <73b20cd6-4b4f-a060-8c37-e9df9793e44b@twiddle.net> (raw)
In-Reply-To: <CAFEAcA8V_Zb3kHThShPQshC4=wt2Oof=VoVU35C0-TyusGzC_w@mail.gmail.com>
On 05/10/2018 07:38 AM, Peter Maydell wrote:
> Thanks. Do we care about trying to follow up on the gcc side
> to find out if this is a definitely-fixed bug?
Given I did not see the problem with gcc 6 as shipped with debian 9, I'm not
overly inclined to dig further than that.
r~
next prev parent reply other threads:[~2018-05-10 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 14:36 [Qemu-devel] [PATCH] atomic.h: Work around gcc spurious "unused value" warning Peter Maydell
2018-05-10 14:37 ` Richard Henderson
2018-05-10 14:38 ` Peter Maydell
2018-05-10 14:43 ` Richard Henderson [this message]
2018-05-10 14:58 ` Philippe Mathieu-Daudé
2018-05-10 17:09 ` Paolo Bonzini
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=73b20cd6-4b4f-a060-8c37-e9df9793e44b@twiddle.net \
--to=rth@twiddle.net \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 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).