From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Hacks for building on gcc 7 / Fedora 26
Date: Tue, 18 Jul 2017 08:23:51 +0100 [thread overview]
Message-ID: <20170718072351.GB11927@redhat.com> (raw)
In-Reply-To: <a18cd09c-5dbd-525e-c4a6-8286e3ce2333@redhat.com>
On Mon, Jul 17, 2017 at 12:29:08PM -0500, Eric Blake wrote:
> On 07/17/2017 11:46 AM, Dr. David Alan Gilbert wrote:
>
> >> +++ w/hw/usb/bus.c
> >> @@ -407,8 +407,9 @@ void usb_register_companion(const char *masterbus,
> >> USBPort *ports[],
> >> void usb_port_location(USBPort *downstream, USBPort *upstream, int portnr)
> >> {
> >> if (upstream) {
> >> - snprintf(downstream->path, sizeof(downstream->path), "%s.%d",
> >> - upstream->path, portnr);
> >> + int l = snprintf(downstream->path, sizeof(downstream->path),
> >> "%s.%d",
> >> + upstream->path, portnr);
> >> + assert(l < sizeof(downstream->path));
> >
> > You may find this doesn't help in some windows builds; the assert
> > functions aren't always marked as noreturn (because they pop up a dialog
> > that asks you whether you want to run into a debugger etc).
>
> How would it not help? Are we using gcc 7 on windows builds? Adding
> the assert is enough to shut up new gcc; old gcc was already silent; and
> if mingw is still on old gcc, it doesn't matter whether assert() is
> marked noreturn for what this patch is doing.
Mingw isn't using a fork of GCC anymore, its all mainline. Thus Fedora's
mingw gcc packages track native gcc packages. IOW i686-w64-mingw32-gcc
is already on version 7.1.0 in Fedora
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 :|
next prev parent reply other threads:[~2017-07-18 7:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 14:38 [Qemu-devel] Hacks for building on gcc 7 / Fedora 26 Dr. David Alan Gilbert
2017-04-07 19:21 ` Philippe Mathieu-Daudé
2017-07-13 13:07 ` Philippe Mathieu-Daudé
2017-07-17 13:42 ` Eric Blake
2017-07-17 13:48 ` Eric Blake
2017-07-17 14:16 ` Gerd Hoffmann
2017-07-17 15:04 ` Eric Blake
2017-07-17 16:46 ` Dr. David Alan Gilbert
2017-07-17 17:22 ` Peter Maydell
2017-07-17 17:29 ` Eric Blake
2017-07-17 17:36 ` Peter Maydell
2017-07-17 18:10 ` Eric Blake
2017-07-17 18:48 ` Dr. David Alan Gilbert
2017-07-18 15:04 ` Philippe Mathieu-Daudé
2017-07-18 15:10 ` Eric Blake
2017-07-19 7:15 ` Thomas Huth
2017-07-17 17:46 ` Dr. David Alan Gilbert
2017-07-18 7:23 ` Daniel P. Berrange [this message]
2017-07-18 12:35 ` Eric Blake
2017-07-18 12:56 ` Daniel P. Berrange
2017-07-18 23:59 ` Richard Henderson
2017-07-19 0:34 ` Eric Blake
2017-04-12 23:54 ` no-reply
2017-07-20 10:50 ` Daniel P. Berrange
2017-07-20 12:10 ` Eric Blake
2017-07-20 16:15 ` Dr. David Alan Gilbert
2017-07-20 16:47 ` Daniel P. Berrange
2017-07-20 17:04 ` Dr. David Alan Gilbert
2017-07-20 17:06 ` Daniel P. Berrange
2017-07-20 18:36 ` Eric Blake
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=20170718072351.GB11927@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@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).