linux-kernel - Re: Paravirt compile failure with gcc33

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4B73206A.2030406@zytor.com>
Date:	Wed, 10 Feb 2010 13:08:58 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jan Engelhardt <jengelh@...ozas.de>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Jeremy Fitzhardinge <jeremy@...source.com>,
	virtualization@...ts.osdl.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Paravirt compile failure with gcc33

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/