On Fri, 2015-03-13 at 14:54 +0100, Matthias Klose wrote: > clone 778181 -1 > reassign -1 src:xen > thanks > > from the upstream discussion, it doesn't seem to be clear if this is a GCC > issue. Is this new in GCC 5?
The first I've heard of it was via this bug report and nobody (me included) seems to be having the issue with gcc 4. I routinely build with Wheezy's compiler, as does the upstream automated test infrastructure. I've just given it a go with "gcc (Debian 4.9.1-19) 4.9.1" (from a slightly old Jessie) and it was ok too. > your referenced bug number seems a bit old (PR57725). > > in http://lists.xen.org/archives/html/xen-devel/2015-03/msg01692.html > PR64963 is referenced, but which is marked as fixed upstream. Closed on 16 February though and the gcc-5 snapshot I was using was dated 20150204, because my apt update for some reason didn't upgrade this old chroot properly and I didn't notice. I've just installed 5-20150307-1 and the issue has gone. I've closed this Xen bug, but I guess there is a clone floating around on the gcc-5 now? > in http://lists.xen.org/archives/html/xen-devel/2015-03/msg01694.html > you write that you suppose I will take this upstream, without noting me. No I > will not. Please do the bike shedding with upstream yourself ;) Sorry, that should have ended "...or he'll ask us to do it" but I was too lazy to type it. Ian. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1426256382.32572.155.ca...@debian.org