From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RFC] QEMU KVM target -> Anthony Date: Sun, 18 Mar 2007 20:39:33 -0500 Message-ID: <45FDE9D5.7030909@codemonkey.ws> References: <3810d4-k6b.ln1@tux.abusar.org> <45FD6C74.1090204@codemonkey.ws> <45FD9853.6040907@codemonkey.ws> <3gl0d4-38g.ln1@tux.abusar.org> <7t01d4-o0j.ln1@tux.abusar.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: =?ISO-8859-1?Q?D=E2niel_Fraga?= Return-path: In-Reply-To: <7t01d4-o0j.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org D=E2niel Fraga wrote: > On Sun, 18 Mar 2007 16:08:21 -0700 > "Ed Swierk" wrote: > > = >> Please read this email thread if you want to know why your assumption >> is incorrect: >> http://lists.gnu.org/archive/html/qemu-devel/2006-10/msg00175.html >> = > > I read everything. The last message by Paul Brook: > > "- qemu makes assumptions about the layout of the code gcc generates. > This works by chance on older gcc. This effects all hosts, and is not a g= cc bug. > > - qemu reserves several registers for its own use. On architecturally cri= ppled = > hosts (ie. x86) this means we hit really obscure gcc bugs on x86 because = gcc = > runs out of registers. This is a gcc bug, but is also relatively easy to = > workaround". > > He even proposes a solution: > > https://nowt.dyndns.org/ > > And even this way, nobody agreed with each other... > > So I ask: if Paul Brook could fix this, why it isn't merged? A > solution should be applied. What we can't do is keep discussing forever > this and the previous message is realy annoying: > = This is qops which is why I said "qops is the right solution" in my = previous note. It's a huge, fundamental change to QEMU so it needs some = time being developed outside of the main tree. I understand that it's frustrating to depend on gcc3. Please realize = though that if it was simple to fix than it would be fixed and more = importantly, that the work is being done to fix the situation. Regards, Anthony Liguori > "Basically, gcc changed in a way that broke qemu. There's been an open > bug report in gcc ever since, but the GCC developers really aren't intere= sted in = > backwards compatability. (Heck, gcc 4.0 breaks building bash 2.05b). Th= e = > qemu developers aren't interested in applying ugly patches to support gcc= 4.x = > until gcc 3.x becomes so obsolete nobody ships it anymore. (And consider= ing = > that there are still some niche embedded boards that have hacked up versi= ons = > of gcc 2.95 targeting them and nothing else, I wouldn't be surprised if i= n = > five years we have your main compiler and the compiler to build qemu, ala = > kgcc under Red Hat 7. *shrug*)" > > It's like saying: "we don't care. Keep using gcc3". :( > > = ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE= VDEV