From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36299) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRVqC-0006ZJ-98 for qemu-devel@nongnu.org; Sun, 24 Jul 2016 22:42:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bRVq8-0005Jr-9R for qemu-devel@nongnu.org; Sun, 24 Jul 2016 22:42:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36097) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRVq8-0005Ji-2I for qemu-devel@nongnu.org; Sun, 24 Jul 2016 22:41:56 -0400 Date: Mon, 25 Jul 2016 10:41:52 +0800 From: Fam Zheng Message-ID: <20160725024152.GA10856@ad.usersys.redhat.com> References: <1469036440-4562-1-git-send-email-mst@redhat.com> <20160721103632.GF32544@pxdev.xzpeter.org> <20160722011337.GA21282@ad.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PULL v3 00/55] pc, pci, virtio: new features, cleanups, fixes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers On Fri, 07/22 10:46, Peter Maydell wrote: > On 22 July 2016 at 02:13, Fam Zheng wrote: > > On Thu, 07/21 11:45, Peter Maydell wrote: > >> It failed on several of my test builds, not just one, but these > >> things are tricky to avoid if they don't happen on all compilers. > >> In this case I think it is a compiler bug: > >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119 > >> so you'll only see it with an older compiler. > > > > Could you name the distro and gcc version? If it's worth to keep the buggy > > compiler happy, it probably can be added as a docker test. :) > > I think ubuntu trusty stock gcc and the clang on OSX, probably > others too. We do have ubuntu trusty docker image, but I don't see the failure with this pull req. Adding an OSX image to docker is much trickier, so I've not really looked into that, yet. Could you give me an exact gcc version number that triggers the thing, to test again? Thanks, Fam