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 20:23:32 -0300 [thread overview]
Message-ID: <k8u0d4-6ai.ln1@tux.abusar.org> (raw)
In-Reply-To: 20070318223654.GA19701@jim.sh
On Sun, 18 Mar 2007 18:36:54 -0400
Jim Paris <jim-XrPbb/hENzg@public.gmane.org> wrote:
> Why not install them both? Most distributions make it quite easy.
> For Debian/Ubunty, "apt-get install gcc-3.3" and you'll have it in 60
> seconds. If you want to remove it when you're done, it's just as
> quick.
Just an analogy: it's this kind of thing that allow companies
like Sun and Adobe to take forever to release a 64bit plugin, for
example. Just because people can run the plugin on 32bit... I disagree
with this. I think that if we have a 64 bit machine, we should be able
to use it in pure 64bit mode and the software should follow the
hardware evolution.
The same applies for gcc. If I have a better gcc, I should be
able to compile qemu with it, instead of using the old gcc3.
gcc is the second most important piece of software in Linux
world, so all the software should follow gcc evolution, since there
isn't another viable compiler (icc isn't a free option).
> I don't think it's appropriate to tell the qemu authors what they
> should be doing. Perhaps the problems are more complicated than you
> believe and they thought their time was better spent elsewhere.
Ok, but at least I think that if someone wants to do something
right, it should put all his/her effort so it will be done right,
otherwise it will result in problems like these. And Anthony's patch
would suffice for kvm's purpose.
But you're correct. i can't blame qemu author if he doesn't
want to support gcc4. I'm just on his hands... At the same time, those
who don't want to use gcc3 will be unable to use kvm because kvm
depends on qemu...
I just think that if KVM uses a patched qemu, it does not mind
if we have patches for the qemu distributed in the kvm tarball, since
it will just be used together with KVM. And as far as I know, the
official qemu won't support kvm, right? So you'll have to maintain your
own qemu version separately.
> GCC 4.x also introduced many new bugs. For a list of just the known
> regressions, see: http://preview.tinyurl.com/ywvpxv
Ok, but when qemu will fully support gcc4? Does it mean we will
have to use gcc3 forever?
Thanks.
--
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-18 23:23 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 [this message]
2007-03-18 23:08 ` Ed Swierk
2007-03-19 0:08 ` Dâniel Fraga
[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=k8u0d4-6ai.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