From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Paravirt compile failure with gcc33
Date: Wed, 10 Feb 2010 13:08:58 -0800 [thread overview]
Message-ID: <4B73206A.2030406@zytor.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1002102019430.6708@obet.zrqbmnf.qr>
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
prev parent reply other threads:[~2010-02-10 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 18:13 Paravirt compile failure with gcc33 Jan Engelhardt
2010-02-10 18:38 ` Jeremy Fitzhardinge
2010-02-10 18:41 ` H. Peter Anvin
2010-02-10 19:20 ` Jan Engelhardt
2010-02-10 21:08 ` H. Peter Anvin [this message]
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=4B73206A.2030406@zytor.com \
--to=hpa@zytor.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.osdl.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).