From: "Dâniel Fraga" <fragabr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] QEMU KVM target -> Anthony
Date: Sun, 18 Mar 2007 21:08:38 -0300 [thread overview]
Message-ID: <7t01d4-o0j.ln1@tux.abusar.org> (raw)
In-Reply-To: c1bf1cf0703181608m23609e17pb43bfce423e6adc5@mail.gmail.com
On Sun, 18 Mar 2007 16:08:21 -0700
"Ed Swierk" <eswierk-t4QvRbHP2kpBDgjK7y7TUQ@public.gmane.org> 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 gcc bug.
- qemu reserves several registers for its own use. On architecturally crippled
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:
"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 interested in
backwards compatability. (Heck, gcc 4.0 breaks building bash 2.05b). The
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 considering
that there are still some niche embedded boards that have hacked up versions
of gcc 2.95 targeting them and nothing else, I wouldn't be surprised if in
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". :(
--
http://u-br.net
Linux 2.6.20: Homicidal Dwarf Hamster
gcc (GCC) 4.1.2
-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-19 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 15:08 [RFC] QEMU KVM target -> Anthony Dâniel Fraga
[not found] ` <3810d4-k6b.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-18 16:44 ` Anthony Liguori
2007-03-18 17:43 ` Dâniel Fraga
[not found] ` <daa0d4-m5d.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-18 19:51 ` Anthony Liguori
2007-03-18 20:53 ` Dâniel Fraga
[not found] ` <3gl0d4-38g.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-18 22:36 ` Jim Paris
2007-03-18 23:23 ` Dâniel Fraga
2007-03-18 23:08 ` Ed Swierk
2007-03-19 0:08 ` Dâniel Fraga [this message]
[not found] ` <7t01d4-o0j.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-19 1:39 ` Anthony Liguori
2007-03-19 2:01 ` Dâniel Fraga
-- strict thread matches above, loose matches on Subject: below --
2007-03-18 22:42 Gregory Haskins
2007-03-18 22:50 ` Dâniel Fraga
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=7t01d4-o0j.ln1@tux.abusar.org \
--to=fragabr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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