Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756462Ab0BJVNR (ORCPT ); Wed, 10 Feb 2010 16:13:17 -0500 Received: from terminus.zytor.com ([198.137.202.10]:42623 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755797Ab0BJVNQ (ORCPT ); Wed, 10 Feb 2010 16:13:16 -0500 Message-ID: <4B73206A.2030406@zytor.com> Date: Wed, 10 Feb 2010 13:08:58 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1 MIME-Version: 1.0 To: Jan Engelhardt CC: Jeremy Fitzhardinge , Jeremy Fitzhardinge , virtualization@lists.osdl.org, Linux Kernel Mailing List , Ingo Molnar , Thomas Gleixner Subject: Re: Paravirt compile failure with gcc33 References: <4B72FD09.1020202@goop.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1235 Lines: 33 On 02/10/2010 11:20 AM, Jan Engelhardt wrote: > On Wednesday 2010-02-10 19:38, Jeremy Fitzhardinge wrote: > >> On 02/10/2010 10:13 AM, Jan Engelhardt wrote: >>> As I was compile-testing 2.6.33-rc with gcc-3.3, >>> binutils-2.19.51-10.26.4.x86_64, I observed a failure when >>> CONFIG_PARAVIRT is turned on: >>> >> >> Yeah, there's a gcc bug of some kind there, and its very hard to see how to >> work around it. When we last discussed this, I think we were close to deciding >> to obsolete gcc 3.3. >> >> HPA, do you remember? > > In fact, there's such a big bug in there that I'll get a runaway > allocation later on when kvm.o is to be compiled. This is getting fun, > but I am absolutely fine with obsoleting 3.x :) I have heard of some people using 3.4, but I'm not sure if anyone cares for current kernels and for x86, in particular. Some other architectures might still be stuck on 3.x. For x86 in particular 3.x support is becoming more of a headache than a help. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/