On Wednesday 2010-02-10 19:38, Jeremy Fitzhardinge wrote:
On 02/10/2010 10:13 AM, Jan Engelhardt wrote:
quoted
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 :)