From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH] usb: Fix clang build
Date: Wed, 20 Jan 2021 09:49:26 +0000 [thread overview]
Message-ID: <20210120094926.GD3015589@redhat.com> (raw)
In-Reply-To: <fd1b9e5f-5436-2cd7-d97a-c6136ce43c95@redhat.com>
On Wed, Jan 20, 2021 at 12:20:43AM +0100, Philippe Mathieu-Daudé wrote:
> Hi Eric,
>
> On 1/20/21 12:07 AM, Eric Blake wrote:
> > ../hw/usb/dev-uas.c:157:31: error: field 'status' with variable sized type 'uas_iu' not at the end of a struct or class is a GNU extension [-Werror,-Wgnu-variable-sized-type-not-at-end]
> > uas_iu status;
> > ^
> >
> > Fix this by specifying a size for the add_cdb member; and at present,
> > the code does not actually use that field other than for the size
> > chosen for the packed uas_iu_command struct, and the choice of one
> > byte does not change the size of the uas_iu union.
>
> I sent a maybe safer approach (from the bus PoV):
> https://www.mail-archive.com/qemu-block@nongnu.org/msg79192.html
>
> Do you mind reviewing it?
>
> >
> > Signed-off-by: Eric Blake <eblake@redhat.com>
> > ---
> >
> > I'm not sure why none of our CI tools pick up this particular clang
> > build failure; I hit it on Fedora 33 when configuring to build the
> > entire tree with clang.
>
> Same issue after upgrading to f33. I sent a patch to bump our CI:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg774117.html
>
> To track Fedora releases I was thinking about a gitlab job checking
> if we are using the latest, else failing; smth as:
>
> $ curl https://getfedora.org/ | grep -q 'Fedora 33 released'
We'd be better off just adding a job that targets Fedora rawhide IMHO so
we get immediate notice that a toolchain update is going to hurt us, instead
of waiting until the next Fedora is already released to find the problem.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2021-01-20 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 23:07 [PATCH] usb: Fix clang build Eric Blake
2021-01-19 23:20 ` Philippe Mathieu-Daudé
2021-01-19 23:26 ` Philippe Mathieu-Daudé
2021-01-20 9:49 ` Daniel P. Berrangé [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=20210120094926.GD3015589@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=kraxel@redhat.com \
--cc=philmd@redhat.com \
--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).