public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Paris <jim-XrPbb/hENzg@public.gmane.org>
To: "Dâniel Fraga" <fragabr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] QEMU KVM target -> Anthony
Date: Sun, 18 Mar 2007 18:36:54 -0400	[thread overview]
Message-ID: <20070318223654.GA19701@jim.sh> (raw)
In-Reply-To: <3gl0d4-38g.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>

> 	I like to have only the latest versions of software installed
> here. For me, it doesn't make sense to use gcc3 only to be able to
> compile qemu, since I'll not use it on any other software.

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.

> 	Well, to be honest, I think that qemu author should have
> migrated to gcc4. I can't understand why someone still uses gcc3 for
> development. I mean, the author could take a weekend and fix all the
> code to compile with gcc4. Is it so hard? I think it's the natural order
> of things.

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.

> 	We should get rid of old things, as fast as possible.
> Gcc3 has no future, so why keep using it?
> 
> 	Besides that, gcc4 offers a lot of options that gcc3
> doesn't. It's faster, I can use its vectorizer and optimizes better the
> code. If it takes too long, we'll have gcc 4.3 and qemu will be still
> requiring gcc3. Don't you think it's absurd?

GCC 4.x also introduced many new bugs.  For a list of just the known
regressions, see:  http://preview.tinyurl.com/ywvpxv

-jim

-------------------------------------------------------------------------
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

  parent reply	other threads:[~2007-03-18 22:36 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 [this message]
2007-03-18 23:23                 ` Dâniel Fraga
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=20070318223654.GA19701@jim.sh \
    --to=jim-xrpbb/henzg@public.gmane.org \
    --cc=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