From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 0/9] bitmap export over NBD
Date: Fri, 22 Jun 2018 09:46:37 -0500 [thread overview]
Message-ID: <6f1a7d16-79af-aa06-af33-e349a08aa53e@redhat.com> (raw)
In-Reply-To: <CAFEAcA_DR6xftAT0wjbHaD=8FxJF0BmS7x=8SmgWtRW+m=-Fcw@mail.gmail.com>
On 06/22/2018 07:13 AM, Peter Maydell wrote:
> On 22 June 2018 at 13:12, Eric Blake <eblake@redhat.com> wrote:
>> Uurgh. It's a false positive (the compiler is complaining that the variable
>> is uninitialized, which can only happen if the while loop is not executed;
>> but the preconditions guarantee the loop executes at least once). The
>> assert() that I added was enough to silence gcc 7.3.1 on my Fedora 27
>> system, but docker-mingw@fedora is using gcc-8.1.1-1.fc28.x86_64. This
>> should silence things (another way to silence would be rewriting while{}
>> into do{}while). I'll submit this as a formal patch if I can reproduce the
>> problem/fix on docker.
>
> Huh. I had thought this was an old-gcc problem, not a new-gcc
> one. Might be worth submitting to the gcc folks as a regression...
Hmm, I couldn't quickly reproduce it with a direct gcc on Fedora 28; and
I don't know docker well enough to know if the cross-gcc used in
docker-mingw@fedora is a different version than the native gcc-8.1.1
listed in the installed packages list (the patchew output doesn't list
the version of x86_64-w64-mingw32-gcc). Thus, I can't tell if it is a
recent gcc regression or merely an old-gcc issue. But I can confirm
that 'make docker-test-mingw@fedora' reproduced the problem without my
cleanup patch, and that my cleanup patch now in master made that happy
again.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-06-22 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 14:57 [Qemu-devel] [PULL v2 0/9] bitmap export over NBD Eric Blake
2018-06-21 14:57 ` [Qemu-devel] [PULL v2 2/9] nbd/server: Reject 0-length block status request Eric Blake
2018-06-21 14:57 ` [Qemu-devel] [PULL v2 6/9] nbd/server: implement dirty bitmap export Eric Blake
2018-06-21 14:57 ` [Qemu-devel] [PULL v2 9/9] nbd/server: introduce NBD_CMD_CACHE Eric Blake
2018-06-22 9:57 ` [Qemu-devel] [PULL v2 0/9] bitmap export over NBD Peter Maydell
2018-06-22 11:43 ` Peter Maydell
2018-06-22 12:12 ` Eric Blake
2018-06-22 12:13 ` Peter Maydell
2018-06-22 14:46 ` Eric Blake [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=6f1a7d16-79af-aa06-af33-e349a08aa53e@redhat.com \
--to=eblake@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).